Electronic device security and tracking system and method

ABSTRACT

A system and method for securing and tracking an electronic device. The system includes hardware, software and firmware components that cooperate to allow tracking, disabling, and other interaction with the stolen electronic device. The system includes an application component, non-viewable component and Basic Input/Output Subsystem (BIOS) component that are present on the electronic device. The BIOS component maintains the secured environment of the application and non-viewable components. If only the application component was provided, a simple low level format of the hard disk drive would remove the application and bypass the security features. The system implements an “application and BIOS” based solution to electronic device security.

CROSS REFERENCE TO RELATED APPLICATION

This application claims priority under 35 USC §119(e)(1) of Provisional Application No. 60/497,182, filed Aug. 23, 2003, incorporated herein by reference.

BACKGROUND

Theft of electronic devices containing costly hardware and software has become increasingly common. Such thefts may occur because of the value of the electronic device hardware or for access to information contained on the electronic device's storage accessories such as credit card information, confidential and proprietary business information, and so on. Another use of the stolen device may be to gain access to servers containing confidential information through the electronic device.

Physical attachment of the electronic device to the user or an immovable object is one way of preventing theft. Password protection schemes may also be used to discourage theft or at least stop the thief from accessing the information stored on the electronic device. Motion sensors or alarms placed on the electronic device may be another impediment to the would be thief. However, such techniques do not always prevent theft, are costly and once the electronic device is stolen, do not allow tracking or recovery.

SUMMARY

The problems noted above are solved in large part by the electronic device security and tracking system and method (ESTSM) that includes a plurality of hardware, software and firmware components that cooperate to allow tracking, disabling, and other interaction with the stolen electronic device. The ESTSM electronic device (hereinafter “electronic device”) and the ESTSM server computer system communicate over a communication channel to determine if the user has registered for ESTSM services. The user may be an individual consumer user or a corporate/government user. The corporate/government user's electronic device may be part of a corporation's or government organization's customized ESTSM system. If the electronic device is not registered for ESTSM services, then upon first time power-on and connection to the ESTSM server of the electronic device that includes ESTSM software and firmware, the user is prompted to register for different ESTSM services. Alternatively, ESTSM may remain disabled and the user may register using techniques that include but are not limited to selecting a menu option for registration or selecting an icon on the electronic device's desktop, or via World Wide Web pages from a remote system other than the ESTSM device itself. The electronic device may be a laptop computer, desktop computer, wearable computer, server computer system, personal digital assistant (PDA), cellular telephone, smart telephone, tablet personal computer, palm top device and so forth. Each of the services may consist of different monthly, yearly or multi-year service fees or a one time fee for the life of the electronic device. After registration is complete, the ESTSM server computer system communicates over the Internet with the user to determine if an electronic device has been reported stolen. In accordance with the preferred embodiment of the invention, if the device is reported stolen, the ESTSM server may inform the ESTSM device via a secure communications channel to take the appropriate action based on the service options selected by the user (e.g. disabling the electronic device, destroying the storage device (e.g. hard disk drive (HDD)) data, recovering data, encrypting data and more). In another embodiment of the invention, an automated voice prompting system at a call center or live call center operator after authentication of the user may communicate with the user to perform ESTSM activities. All ESTSM activities performed through the Internet may also be performed by the call center including registration, reporting a system stolen, reporting system has been recovered and so forth.

The ESTSM system may include an electronic device with three components and a server computer system. The three components may be an application component, a non-viewable component and a Basic Input/Output System (BIOS) component. In the preferred embodiment of the invention, the application component includes ESTSM application software that executes under any Windows® operating system (OS). In other embodiments of the invention, the application component software may execute under the Disk Operating System (DOS), Linux operating system, Windows® CE (and its derivatives such as Windows® Mobile, SmartPhone, Pocket PC, and so on), Symbian and Palm operating system and others. In some embodiments of the invention, the application component is responsible for communicating over the Internet with the ESTSM server computer system to determine if the electronic device has been reported stolen. If the device has been reported stolen, the application component along with the ESTSM server computer system will determine what services the user has registered for and will take the appropriate action (e.g. disable the device, communicate identifying information to the server, erase the storage device, recover data, encrypt data, etc).

In some embodiments of the invention, the communication medium may be a messaging protocol such as short messaging service (SMS) used in mobile devices such as cell phones. In such systems, the server computer system would inform the application component that the device had been reported stolen without the application component querying the server system to determine if the electronic device has been reported stolen.

In the preferred embodiment of the invention, the non-viewable component may reside in a hidden partition on the hard disk drive HDD. Alternatively, in another embodiment of the invention, the non-viewable component may reside in the Host Protected Area (HPA) of the HDD that is not accessible by the operating system of the electronic device. The non-viewable component may include a VALIDATOR program that inspects an ESTSM Communications Area (ECA) to determine if the ESTSM application components have run correctly during the last system boot. The non-viewable component may also contain a copy of the original application component software fileset if the files need to be re-installed to the HDD.

ESTSM also consists of a BIOS component that maintains the secured environment of the ESTSM application component. The BIOS component includes a secure nonvolatile area that stores critical information present after electronic device power-off and accessible during electronic device power-on and boot. If only the application component was provided, a simple low level format of the hard disk drive would remove the application and bypass all the security features. ESTSM implements an “application, BIOS and non-viewable component” based solution to electronic device security. The ESTSM BIOS components ensure that a thief cannot bypass or circumvent the ESTSM application from running.

On every boot, the BIOS component will check and ensure that the ESTSM application components have not been deleted or tampered with. If the BIOS component detects a problem with any of the application components, it will restore the components from a special hidden partition on the hard disk drive or from system recovery media. In the preferred embodiment of the invention, the recovery media may be a floppy diskette but in other embodiments the recovery media may be a Compact Disc-Read Only Memory (CD-ROM), Universal Serial Bus (USB) key storage device, or other storage device accessible during device boot.

In another embodiment of the invention as mentioned above, the electronic device in the ESTSM may include a HDD that contains a HPA. The HPA is not accessible by the operating system of the electronic device or by the user of the electronic device. An ESTSM application component including ESTSM application software may be present on the HDD. The HPA may include an ESTSM non-viewable component. The ESTSM electronic device may also include an ESTSM BIOS component that is capable of communicating with the non-viewable component and application component. An ESTSM server computer system communicates with the other components through an ESTSM Communications Area (ECA) located on the HDD.

In some embodiments of the invention, the ESTSM system may include an electronic device with a BIOS component, an application component and a server computer system. On every boot, the BIOS component will check and ensure that the ESTSM application components have not been deleted or tampered with. If the BIOS component detects a problem with any of the application components, it will assume that the ESTSM application components will be installed by the user of the electronic device. If the application component is not installed after a number of unsuccessful attempts, the BIOS component will prevent the user from accessing the electronic device. The application component may be installed by downloading from the ESTSM website or from recovery media that came with the device.

In another embodiment of the invention, the electronic device in the ESTSM includes a Flash memory and may be a PDA or mobile cellular telephone. The Flash memory may contain a changeable area and a system area. The system area is not changeable by the user of the electronic device. The ESTSM application software may reside in the changeable area or the system area depending on the security requirements of the device implementation. An ESTSM server computer system communicates to the ESTSM application software on the electronic device through communication channels that may be the Internet, a wireless medium (such as SMS), a combination of the two, and so on. The PDA or mobile cellular telephone may be continuously connected to the ESTSM server computer system through an always-on Internet connection.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a screen shot of the registration reminder for the ESTSM;

FIGS. 2 a-2 b show screen shots of the service offerings and selection page for the ESTSM;

FIGS. 3 a-3 c shows screen shots of the user registration and information input pages for the ESTSM;

FIG. 4 shows a screen shot of a new user registration email sent to a user after they have registered their electronic device with ESTSM;

FIG. 5 shows a screen shot of the login page for connecting to ESTSM server computer system in accordance with one preferred embodiment of the invention;

FIG. 6 shows a screen shot of the device registry web page that resides in the ESTSM server computer system in accordance with the preferred embodiment of the invention;

FIG. 7 shows a screen shot of the electronic device status web page that resides in the ESTSM server computer system in accordance with the preferred embodiment of the invention;

FIGS. 8 a-8 b show screen shots of web pages that allow a user to report a stolen electronic device in accordance with the preferred embodiment of the invention;

FIG. 9 shows a screen shot of an email containing location identification information for a stolen electronic device in accordance with the preferred embodiment of the invention;

FIG. 10 shows a screen shot from another computer system that can display web pages of a registration web page for ESTSM on a PDA;

FIG. 11 shows a screen shot of the service offerings for an ESTSM enabled PDA using another computer system capable of displaying web pages;

FIG. 12 shows a screen shot for registration of a PDA with ESTSM in accordance with one preferred embodiment of the invention that requests the user enter the registration key on their PDA;

FIG. 13 shows for one preferred embodiment of the invention a screen shot from a Pocket PC requesting the user enter the registration key shown in FIG. 12;

FIG. 14 shows a screen shot from a Pocket PC displaying a confirmation key generated after the user enters the registration key;

FIG. 15 shows a screen shot from a computer system capable of displaying web pages of Pocket PC verification requesting the user enter the confirmation key from the Pocket PC display;

FIG. 16 shows a screen shot from a computer system capable of displaying web pages of a successful registration message for a PDA;

FIG. 17 shows a screen shot from a computer system capable of displaying web pages indicating that the PDA is currently secured;

FIG. 18 shows a screen shot of the user authentication screen in accordance with one preferred embodiment of the ESTSM invention that may be used by a call center operator to verify the identity of a user;

FIG. 19 shows a screen shot of the welcome page for corporate administration of ESTSM;

FIG. 20 shows a screen shot of corporate information input and modification by the administrator;

FIG. 21 shows a screen shot of a web page that allows a corporate administrator to register a user for ESTSM;

FIG. 22 shows a screen shot of a web page that allows a corporate administrator to remove a user's access to ESTSM;

FIG. 23 shows a screen shot of a web page that allows a corporate administrator to purchase licenses for services in ESTSM;

FIG. 24 shows a screen shot of a web page that allows a corporate administrator to purchase licenses to upgrade or modify services in ESTSM;

FIG. 25 shows a screen shot of a web page that allows a corporate administrator to give permission to users to report their computer stolen in accordance with the preferred embodiment of the invention;

FIG. 26 shows a screen shot of a web page showing menu options selectable by a corporate administrator for administration of ESTSM;

FIG. 27 shows a screen shot of a web page that allows a corporate administrator to create a corporate ESTSM account and register a super-user;

FIGS. 28 a-28 b show screen shots of a web page requesting a corporate administrator to enter a purchase order quotation number for basic or upgraded ESTSM services;

FIG. 29 shows a screen shot of a web page that allows a corporate administrator to send an email to a user indicating activation of ESTSM;

FIG. 30 shows a screen shot of a web page that allows a corporate administrator to reset a login and password for a user;

FIG. 31 shows a screen shot of a web page that allows a corporate administrator to override ESTSM on an electronic device using a generated password;

FIG. 32 shows a screen shot of a web page that allows a corporate administrator to stop a machine or user from accessing ESTSM services;

FIG. 33 shows a screen shot of a web page that allows a corporate administrator to view the status of an electronic device using the machine id or a user login assigned to the device;

FIG. 34 shows a screen shot of a web page that allows a corporate administrator to recover an electronic device that has been reported stolen using a generated password;

FIG. 35 shows a screen shot of a web page that allows a corporate administrator to change the settings of the ESTSM server;

FIGS. 36 a-36 b show screen shots of web pages that allow a corporate administrator to change administrator login and master passwords;

FIG. 37 shows the state transitions of an electronic device from a not registered state to registered and active state;

FIG. 38 shows the state transitions of an electronic device from a not registered state to registered and active state with the device passing through a never remind state;

FIG. 39 shows the state transitions of an electronic device from a registered and active state to deregistered state;

FIG. 40 shows the state transitions of an electronic device with ESTSM that is reported stolen and then recovered;

FIG. 41 shows the state transitions of an electronic device from a registered and active state to override state;

FIG. 42 shows the states of an electronic device registered- and active with ESTSM and including the data destroy service;

FIG. 43 shows the states of an electronic device registered and active with corporate ESTSM in which the corporate user of the device is removed from ESTSM;

FIG. 44 shows the architecture of ESTSM including an electronic device and server computer system in accordance with one embodiment of the invention;

FIG. 45 shows the architecture of ESTSM in accordance with another embodiment of the invention for PDA connected to server computer system;

FIG. 46 shows another embodiment of the ESTSM architecture including an electronic device and server computer system;

FIG. 47 shows another embodiment of the ESTSM architecture including an electronic device with a WWW component and server computer system;

FIG. 48 shows the architecture of ESTSM in accordance with another embodiment of the invention for an electronic device with SMS connected to server computer system;

FIG. 49 shows a schematic of a computer system that includes a BIOS component, application component and non-viewable component in accordance with one embodiment of the invention;

FIG. 50 shows a schematic of a cellular telephone that includes an application component in a system area in accordance with another embodiment of the invention;

FIG. 51 shows a schematic of the ESTSM server computer system of FIGS. 44-47 in more detail in accordance with the preferred embodiment of the invention;

FIG. 52 shows the connections between the primary and secondary servers contained in the web server of FIG. 51 in accordance with the preferred embodiment of the invention;

FIG. 53 is a flow diagram of the BIOS component of the ESTSM in accordance with some preferred embodiments of the invention;

FIG. 54 is a flow diagram of the VALIDATOR program in the non-viewable component of the ESTSM in accordance with some preferred embodiments of the invention;

FIG. 55 is a flow diagram of the application component of the ESTSM in accordance with some preferred embodiments of the invention;

FIG. 56 shows encrypted and encoded communication between a client electronic device and the ESTSM server computer system in accordance with the preferred embodiment of the invention;

FIG. 57 shows encryption and encoding of information by the client electronic device and decoding and decryption of information by the server computer system;

FIG. 58 is a flow diagram implemented in the client and server for encoding binary data into text format data in accordance with the preferred embodiment of the invention;

FIG. 59 is a flow diagram implemented in the client and server for decoding text format data into binary data in accordance with the preferred embodiment;

FIG. 60 is a flow diagram showing encryption and encoding of SMS messages from SMS server to SMS enabled ESTSM electronic device in accordance with the preferred embodiment of the invention;

FIG. 61 is a flow diagram showing decoding and decryption of SMS messages in accordance with some embodiments of the invention;

FIG. 62 a is a flow diagram showing integration of ESTSM BIOS image files into system BIOS of the electronic device in accordance with one embodiment of the invention;

FIG. 62 b is a flow diagram showing integration of the ESTSM option ROM into a Phoenix® BIOS binary image;

FIG. 63 shows in accordance with another embodiment of the invention integration of ESTSM BIOS image files into electronic device system BIOS using BIOS editor;

FIG. 64 shows in accordance with another embodiment of the invention integration of ESTSM BIOS image files into electronic device system BIOS using BIOS Configuration utility;

FIG. 65 show screen shots of the service offerings for the ESTSM mobile device;

FIG. 66 shows screen shots of the user registration and information input pages for the ESTSM mobile device such as a Smartphone;

FIG. 67 shows a screen shot from a computer system capable of displaying web pages of a successful registration message for a mobile device;

FIG. 68 shows a screen shot of the mobile device status web page that resides in the ESTSM server computer system in accordance with the preferred embodiment of the invention;

FIG. 69 shows a screen shot of the backup files web page for a mobile device that resides in the ESTSM server computer system in accordance with the preferred embodiment of the invention;

FIG. 70 shows a screen shot from a mobile device indicating that the device has been disabled;

FIG. 71 is a flow diagram showing implementation of ESTSM on mobile devices; and

FIG. 72 shows the state transitions of a mobile device with SMS messages for activation and operation of ESTSM services.

DETAILED DESCRIPTION

The ESTSM consumer user (i.e. non-corporate user) experience consists of two phases: (1) the registration phase and (2) administration phase via the ESTSM website. In the registration phase, the user creates an account with ESTSM, specifies what ESTSM services he wishes to purchase, and provides user and billing information to complete the registration.

Once registration is complete, the typical user will not interact with ESTSM until the electronic device is stolen. At that time, the user can log into the ESTSM website. Once logged in, the user can report the device as stolen, disable the device, or perform other device administration tasks. The user may also initiate all ESTSM device administration tasks through a call center that can validate the identity of the user and perform administrative tasks on the user's behalf.

After registration is complete, the ESTSM server computer system communicates over the Internet with the user to determine if the electronic device has been reported stolen. In accordance with the preferred embodiment of the invention, if the device is reported stolen, the ESTSM server will instruct the electronic device to take the appropriate action based on the service options selected by the user (e.g. disabling the electronic device, destroying the hard disk drive (HDD) data, recovering data, encrypting data and more).

When the user purchases the electronic device, the ESTSM components may be pre-installed by the manufacturer of the electronic device. In the preferred embodiment of the invention, the ESTSM registration screen shown in FIG. 1 will come up when the user starts using his electronic device and the ESTSM system determines that the electronic device is not registered. The ESTSM system determines if the electronic device is registered or not by communicating with the ESTSM server computer system.

In another embodiment of the invention, the user may request the manufacturer of the device to preregister the user for ESTSM services after the manufacturer builds the electronic device. In some alternative embodiments of the invention, the device may be preregistered for ESTSM services at the location (e.g. retail store) where the device is purchased. Preferably, in one embodiment of the invention, the initial fees for the ESTSM services as described below may be included by the manufacturer in the price of the electronic device or may be discounted as a sales promotion for the device.

In some other embodiments of the invention, the ESTSM system may be provided to the manufacturer of the electronic device without charge or for a very small fee. The user of the device may select the ESTSM services they want and the revenue generated may be shared by the manufacturer and ESTSM administrator. Thus, the user may “opt-in” to purchase the ESTSM services. In some embodiments of the invention, the ESTSM services may be ofered to the user of the electronic device on a trial basis for a limited time.

The user can proceed with the registration process at this point, or choose to register at a later time or never. If the user chooses to register at a later time, the ESTSM will remain disabled and the user may register using techniques that include but are not limited to selecting a menu option for registration or selecting an icon on the electronic device's desktop. If the user proceeds with the registration process, the user will be asked to specify if they are a “new user” or an “existing user” that has other electronic devices running ESTSM. The next stage as shown in FIGS. 2 a-2 b is to choose the ESTSM services for the electronic device.

FIGS. 2 a-2 b shows the service selection screen that may include the cost of each service and the number of services offered. The services offered and the cost of each service may vary based on the manufacturer and model of the electronic device, the market segment of the electronic device (i.e. business device, home use device) and what the manufacturer has chosen to include for the device. Some manufacturers may want to change the pricing of the services, or offer bundled services to the use. For one embodiment of the invention, as shown below, is a list of the typical services available to the user and the associated costs.

-   -   1. Basic Service—with this service the user has the ability to         have the electronic device disabled when it is stolen. However,         the location of the stolen electronic device is not tracked and         no other operation is performed.     -   2. Tracking Service—with this service, the location of the         stolen electronic device will be tracked and the location report         information is sent to the user of the electronic device via         email (or the user can call a monitoring station to get the         information). There are two sub-options under the tracking         service: Track-and-Disable or Continuous Track. In the         Track-and-Disable option, the location of the electronic device         is captured one time and then the electronic device is disabled.         In the Continuous Track option, the location of the electronic         device is constantly tracked until the user manually disables         the electronic device from the ESTSM website. Electronic devices         such as cell phones because they are mobile and cannot be easily         tracked may not offer this service.     -   3. Data Destroy Service—with this service, the hard disk of the         stolen electronic device is erased when the thief connects the         electronic device to the Internet. This service has two         sub-options: (1) Automatically Erase when the electronic device         is connected to the Internet, or (2) Manual Erase, the user must         manually specify when to erase the hard disk drive via the ESTSM         website.     -   4. Third Party Insurance Signup—with this service, ESTSM will         re-direct the user to the website of third party companies that         will assist the user in signing up for theft and damage         replacement insurance for their electronic device.

In some embodiments of the invention, due to the extendible design of ESTSM, new services can be added into the ESTSM registration process as given below:

-   -   1. Data Encryption Service—with this service, a virtual file         folder called “My Encrypted Documents” is created on the desktop         of the electronic device. In some embodiments of the invention,         all files saved in this folder are encrypted by encryption         techniques built into the operating system. Access to the folder         is denied unless the system is connected to the Internet and the         electronic device has not been reported stolen. If the system is         not connected to the Internet, the user can optionally enter the         ESTSM username and password to get access. In another embodiment         of the invention, the user may designate any virtual file folder         in the electronic device as an “ESTSM Encrypted Folder.”     -   2. Data Recovery Service—this service will allow a user to         specify critical files and in the case of theft, the software         will first recover these files to the ESTSM server computer         system, before performing other service option actions. In one         embodiment of the invention, a virtual file folder called “My         Critical Files” is created on the desktop of the electronic         device. The user may store the actual files, copies of files, or         shortcut pointers to files in this folder that they want to         recover if the electronic device is stolen. In another         embodiment of the invention, right clicking a mouse button with         the pointer pointing to a file displays a menu allowing the user         to mark the file as a “Critical File.” The file's icon is         modified to indicate that it will be recovered if the electronic         device is stolen. This embodiment of the invention allows the         file to be present anywhere on the HDD of the electronic device         rather than in a specific file folder. Another embodiment of the         invention may use both the virtual file folder “My Critical         Files” as well as files marked as “Critical Files” to indicate         files that will be recovered if the electronic device is stolen.

In the preferred embodiment of the invention, most of ESTSM services are based on a yearly fee model. Some services such as data recovery may be billed on a per megabyte basis-that is, the user indicates the number of megabytes to be recovered during registration and is billed accordingly. However, if the electronic device is stolen and during data recovery more megabytes are recovered, then a one time fee is charged to the user. The user will automatically be billed at the end of the year to renew the service for one more year. The user will be sent an email before billing to give the user a chance to cancel the service if they wish.

The next stage in the registration phase is to create the username and password as shown in FIGS. 3 a-3 b that can be used to log onto the ESTSM website to report a stolen electronic device, etc. Once that is completed, the user must provide his user information (name, address, phone number, and so forth) as shown in FIG. 3 c so that the monitoring station can identify the user if the user calls the monitoring station to report a theft.

The final part of the registration phase is to provide the billing information for the ESTSM services. This requires the input of a credit card number, debit card number, or checking account number. The information is then validated, the credit card or other billing means is charged and a confirmation email as shown in FIG. 4 is sent to the end user, corporation or insurance company that just completed the registration. The user will have to click a link at the end of the email to activate the ESTSM on that electronic device. In some embodiments of the invention, periodic ESTSM service charges may be billed by adding these charges to the existing electronic device bill. For example, ESTSM monthly service charges may be added to the users' existing mobile phone bill for ESTSM registered mobile phones.

As mentioned above, ESTSM provides a website from which the user may administer the ESTSM services on the electronic device. In some embodiments of the invention, corporate users may have limited administrative capabilities because of their access permissions (described in more detail below). As shown in FIG. 5, the user must first log into the website using the username and password that was created during the registration phase. A user without access to the Internet (i.e. his electronic device was stolen), can call the ESTSM monitoring station to perform the administrative functions described below for the electronic device.

Once the user has logged into the ESTSM website, the main ESTSM menu in accordance with the preferred embodiment of the invention is presented as shown in the left hand portion of FIG. 6. In some embodiments of the invention, corporate and noncorporate users may have different ESTSM menus.

The “Device Registry” portion of the page in FIG. 6 shows all the electronic devices the user currently has registered with ESTSM. By clicking on a device image from the “Device Registry” page of the ESTSM website, the user is taken to the “Device Status” page shown in FIG. 7. On the “Device Status” web page for each device, the user can perform the following tasks: (1) View the status of the user's electronic devices running ESTSM; (2) Report an electronic device stolen; (3) Recover and re-enable a stolen system that has been found; (4) Upgrade or change the ESTSM service options; (5) Show the Billing and Electronic Device Location/Status Logs; (6) Perform User Management functions such as changing the user information, password and billing information; and (7) Perform Data Management functions such as viewing recovered data and transferring recovered data to another device.

As shown in FIGS. 7, the “Device Status” page shows for each electronic device, the Model Name, System Description, Current State, ESTSM Services Active on the Device, and Last Connection to ESTSM Server. Depending on the Current State and the services selected by the user, certain task buttons will appear below the electronic device information. These task buttons let you perform different operations on the device (e.g. report the electronic device stolen and so forth).

As shown in FIG. 7, the user may click on the button labeled “Report Stolen” to start the process of reporting an electronic device stolen. The user will be taken to the “Report a Stolen Device” web pages shown in FIGS. 8 a-8 b. The user fills out the information on the web page to generate a theft incident report and the ESTSM site will log this report so that it may be given later to the appropriate authorities as proof of filing the theft incident report. This documentation may be provided to the user upon request.

Once the report is completed, the electronic device will be put in the REPORTED STOLEN state (states of ESTSM are described in detail below). At this point, if the electronic device is connected to the Internet, the electronic device state will change to either BEING TRACKED or DISABLED state.

In some alternative embodiments of the invention, mobile devices such as cell phones and Smartphones that may be always connected to the ESTSM server and contacted at anytime by the server can communicate through a message passing scheme. Message passing schemes may be SMS, WWW message passing protocol based on Transmission Control Protocol/Internet Protocol (TCP/IP), or Multimedia Messaging Service (MMS). The state diagram for mobile devices are shown in FIG. 72.

If the electronic device is in the BEING TRACKED state, the user will receive an email, an example of which is shown in FIG. 9, documenting the location of the stolen electronic device. This location information may contain the following information: (1) IP address of the stolen electronic device (2) domain name on the Internet 6 f the stolen electronic device (3) owner of the domain name (4) contact information for the domain name owner (5) name and contact information of the Internet Service Provider (ISP) and (6) date and time of IP address connection.

With this information, the user may pursue recovery with the appropriate authorities. The information provided may be used to track the exact location of the electronic device. For example, ISPs may identify the network port, cable modem or phone number from which the electronic device was connected when provided with the IP address, date and time of the connection. A location tracking report email will be sent to the user each time the electronic device is connected to the Internet. If the “Track and Disable” service option is selected, by the user, then only one tracking location will be recorded since the electronic device will be automatically disabled once the location is recorded.

In another embodiment of the invention, ESTSM registration as shown in FIG. 10 for a PDA, mobile cellular telephone, or Smartphone device may be performed using another computer system that can display ESTSM registration web pages. In some preferred embodiments of the invention, a different set of ESTSM services as shown in FIG. 11 may be offered for the PDA. Thus, the manufacturer may offer, but not limited to, a Basic service and a Data backup service for the device as shown in FIG. 11.

After the user has selected the ESTSM services for their PDA, in the preferred embodiment of the invention, the ESTSM system as shown in FIG. 12 may request that the user interact with the ESTSM application on the PDA and enter the registration key into the device as shown in FIG. 13. Entering the registration key into the device may be the first step to start a multi-step registration process that ensures that the correct electronic device is being registered. The PDA will then display a confirmation key as shown in FIG. 14. The user through the computer system capable of displaying ESTSM web pages may then enter into the PDA verification screen shown in FIG. 15 the confirmation key and a system description. The registration process for the PDA is successfully completed as shown in FIG. 16 and the device is secured as shown in FIG. 17. In some other embodiments of the invention, ESTSM registration may not require any user intervention with the ESTSM electronic device except an acknowledgement from the user at the end of the successful registration.

In another embodiment of the invention, an automated voice prompting system at a call center or live call center operator after authentication of the user as shown in FIG. 18 may communicate with the user to perform ESTSM activities. All ESTSM activities performed through the Internet may also be performed by the call center including registration, reporting a system stolen, reporting system has been recovered and so forth.

In most business or government organizations, a central IT staff is responsible for configuring, maintaining and purchasing licenses for electronic devices. ESTSM is designed to work easily in controlled corporate or government environments. Electronic devices registered to corporations or government entities using corporate/government registration may contain a different set of administration pages and user pages as compared to non-corporate users. In one embodiment of the invention, the corporate web pages may be as shown in FIGS. 19-25. Web pages for government entities would be similar to the corporate web pages shown in FIGS. 19-25. Corporate ESTSM systems may be designed to be centrally maintained and administered as required by corporate customers. When a corporate account is created, a central administrator or manager is specified. The central manager can then create other managers and users and purchase and assign licenses to these managers and users as shown in FIGS. 21 and 23-24. As shown in FIG. 21, the central manager can assign user permissions to other managers. Thus, the corporation can control which users are allowed to report stolen electronic devices as shown in FIG. 25, remove users as shown in FIG. 22, purchase more licenses, upgrade services, etc.

For electronic devices registered to corporations or government entities, the ESTSM may contain the user's position within the company and associate user permissions with that position as shown in FIG. 21. Thus, if a user leaves the company, the electronic device may be assigned to another employee transparently and without any change in service fees. The ex-employees account information on ESTSM may be disabled and removed as shown in FIG. 22, so that the ex-employee may not falsely report an electronic device stolen to disable access to the device.

Another embodiment of the registration and administration technique for electronic devices in ESTSM for corporations is shown in FIGS. 26-36 b. A corporate administrator may access the ESTSM server computer system located in the monitoring station by calling the monitoring station or through the Internet. In another embodiment of the invention, the corporation or government entity may have the ESTSM server computer system located within their own premises for greater security and control. In this embodiment of the invention, the administrator can access the server system through a terminal connected to the server or from a computer system at a remote site connected to the server system through the Internet.

The corporate or government entity can setup a corporate account to use ESTSM. The corporation or government entity can purchase services licenses in “bulk” (i.e. 100 Data Destroy Services, 50 Tracking Services, etc). The licenses can be paid for via standard purchasing methods such as Purchase Orders as shown in FIGS. 28 a-28 b, net 30 day terms, etc. The corporation or government entity receives a license number for each purchase. This license number is given to the end users in the corporate or government entity who will consume the license. Alternatively, the corporation or government entity may pay a non-recurring one time fee for individual services.

The corporate or government end user will register in a similar fashion as described above. However, in one preferred embodiment of the invention, when creating the username and password, the user can enter the license number for the “License Number” field as shown in FIG. 3 a. In this embodiment of the invention, the end user will not be required to select the services as they will be determined by the services paid for in the license number. Also, the end user will not have to provide a credit card or other form of payment.

The administrator of the corporate or governmental ESTSM account can manage and configure the electronic devices in the corporation or government entity that have the ESTSM application installed. Thus, for example, the administrator may re-send an activation email to a user of an ESTSM enabled electronic device as shown in FIG. 29 or send a login and password reminder to the user as shown in FIG. 30. The administrator may override an individual user's access to an electronic device as shown in FIG. 31, deregister an electronic device from the ESTSM system, or remove user access to ESTSM enabled electronic devices as shown in FIG. 32. The current state of the electronic device (ACTIVE, REPORTED STOLEN, BEING TRACKED, DISABLED, HALF-RECOVERED, and so on as described in detail below) registered with ESTSM may be viewed by the corporate or government administrator by entering the machine id, the login id of the user, mobile phone number, or any other ESTSM device specific identification as shown in FIG. 33. The administrator can also perform other administrative tasks such as recover an ESTSM enabled system as shown in FIG. 34, change server settings as shown in FIG. 35, or change the administrator login password or administrator master password as shown in FIGS. 36 a-36 b.

The administrator may add new users to the ESTSM system and designate the rights and permissions of users so that these users have administrator capabilities. Users on a corporate or governmental ESTSM account may heave Permission to report their ESTSM device stolen, perform user management functions, and so forth.

As mentioned above and shown in FIG. 7, the “Device Status” page displays task buttons below the electronic device information. The task buttons displayed depend on the current state of ESTSM and the services selected by the user. The task buttons let the user perform different operations on the device (e.g. report the electronic device stolen and so forth).

Each electronic device can have one of the following current states: ACTIVE, REPORTED STOLEN, BEING TRACKED, DISABLED and HALF-RECOVERED. The definition of each of the states is given below:

-   -   1. ACTIVE—This state indicates that ESTSM is actively running on         the electronic device. The electronic device has not been         reported stolen.     -   2. REPORTED STOLEN—This state indicates that the electronic         device has been reported stolen by the user, but the electronic         device in some embodiments of the invention has not communicated         with the ESTSM server after being reported stolen.     -   3. BEING TRACKED—This state indicates that the electronic device         has been reported stolen by the user and the electronic device         has communicated with the ESTSM server. The ESTSM server has         captured location information of the stolen device. Once the         system is in the BEING TRACKED state, other actions can be         performed such as disabling the electronic device (if the         Continuous Track option has been selected) of erasing the hard         disk drive (if Manual Data Destroy Service has been selected).     -   4. DISABLED—The stolen electronic device has been disabled by         ESTSM. The system is now in the locked state and can not be         used. If the system is recovered by the user, they will need to         obtain the activation password to re-enable access to the         electronic device.     -   5. HALF-RECOVERED—This state indicates that the electronic         device has not been totally recovered. The user of the         electronic device has reported that the device has been         recovered. The user must enter the activation password on the         electronic device to re-enable access.

The ESTSM system may also be in one of these other states:

-   -   1. NOT REGISTERED—The electronic device is not registered with         the ESTM system. The device will be in this state if the user         chooses not to register with ESTSM when prompted to do so upon         first time power-on of the electronic device.     -   2. DE-REGISTERED—ESTSM is no longer active on this electronic         device. The user may want to put the electronic device in this         state in the event that the transfer of electronic device from         one user to another is to take place. Once the electronic device         is placed in the DE-REGISTERED state, the user must re-register         the electronic device (which may involve re-paying service fees)         to re-activate the electronic device.     -   3. USER REMOVED—For users of a corporate ESTSM system, the ESTSM         corporate administrator may remove a user's access rights to the         ESTSM system. This situation may occur when the user leaves the         company.     -   4. NEVER REMIND—This state indicates that the user of e         electronic device does not want to be reminded to register with         the ESTSM system. This state may be entered if the user         activates the “Never Remind” option in the registration process.         After activating “Never Remind”, the user may register with         ESTSM by manually selecting “Register Now” option on the ESTSM         application icon and successfully completing the registration         process.     -   5. REGISTERED NOT ACTIVATED—In this state the user has         successfully registered the electronic device through the         registration process but has not clicked on the link sent with         the activation email to complete the registration process.     -   6. GOING TO DISABLE—This state indicates that the user has         selected the “Disable” option after the electronic device has         been reported stolen and is being tracked.     -   7. OVERRIDE—This state indicates that ESTSM has been disabled         temporarily by the user. This may be because the application         component is not able to communicate with the ESTSM server         computer system. To use the electronic device while in this         state, the user enters an activation password when prompted with         a warning.     -   8. ERASE HARDDISK—This state indicates that the user selected         “Data Destroy Services” option when registering with the ESTSM         system. This state is entered after the user reports the         electronic device as stolen and the device is connected to the         Internet and tracked.     -   9. ACTIVATION PENDING—A message has been sent to the electronic         device and the ESTSM server is waiting for an acknowledgment.     -   10. DISABLED DATA BACKUP—This state indicates that the         electronic device is disabled after the data on the electronic         device has been backed up.     -   11. ACTIVE DATA BACKUP—This state indicates that the device has         been re-enabled after it was in the the DISABLED DATA BACKUP         state and a successful acknowledgment is received from the         electronic device. In this state, the user may restore the data         back on the electronic device from the backup on the ESTSM         server.     -   12. BACKUP IN PROGRESS—In this state the electronic device has         been disabled and the ESTSM server is in the process of getting         the data from the device.     -   13. RESTORE IN PROGRESS—The user has requested that the data         backed up on the ESTSM server be restored into the electronic         device and the restore is in progress.

-   14. ENABLE PENDING—This state indicates that the stolen electronic     device has been re-enabled and the ESTSM server has sent the message     to the electronic device and is awaiting acknowledgment.     -   15. ENABLE AFTER RECOVERY—This state indicates that the         electronic device was enabled from either the BACKUP IN PROGRESS         state or the DISABLED DATA BACKUP state. The electronic device         is sent a message and the state is changed after receiving a         confirmation.

Turning now to FIGS. 37-44 and FIG. 72, state diagrams including the states described above and the conditions to enter and exit the states are shown. FIG. 37 shows the states and transitions of an electronic device in ESTSM from a not registered state to registered and active state. After the user goes through the registration process 3720, an electronic device in the not registered state 3710 transitions into the registered and not activated state 3730. Once the user clicks on an activation email 3740 on the electronic device or calls an activation telephone number, the device becomes registered and active 3750.

Referring to FIG. 38, the states and transitions of an electronic device in ESTSM from a not registered state to registered and active state with the device passing through a never remind state are shown. If the user clicks the never remind option shown in FIG. 1, the electronic device transitions 3820 to the never remind state 3830. Next, if the user at a later time decides to manually register (i.e. in some embodiments of the invention by clicking on an ESTSM application icon on the graphical interface of the device and going through registration process), the electronic device is placed into a registered and not activated state 3850. Once the user clicks on an activation email 3860 on the electronic device or calls an activation telephone number, the device becomes registered and active 3870.

Referring to FIG. 39, the states and transitions of an electronic device in ESTSM from a registered and active state to deregistered state are shown. The user may decide they no longer want ESTSM services and select the “Stop ESTSM” option 3920 shown in FIG. 7. The electronic device that was previously in the registered and active state 3910 will transition to the deregistered state 3930 after selection of “Stop ESTSM.”

Referring to FIG. 40, the states and transitions of an electronic device in ESTSM that is reported stolen and then tracked, disabled, and recovered are shown. During registration and activation with ESTSM, the user must select the Track and Disable service option to activate the states and transitions shown in FIG. 40. Once the electronic device is registered and active with ESTSM 4010 and the user reports the system stolen 4015, ESTSM will place the device into the reported stolen state 4020. When the electronic device is next connected to the Internet, ESTSM will begin tracking the device in the being tracked state 4030. The user is sent a location identification email shown in FIG. 9 and because the user had selected the track and disable service is again given the option to disable 4035. If the user selects disable 4035 then the electronic device is placed into the going to disable state 4040. The Application component on the electronic device disables the device 4045 and informs the ESTSM server computer system that the electronic device is in a disabled state 4050. If the user recovers the device and performs the recovery procedure 4055, the electronic device is placed into the half recovered state 4060. Next, the application component on the electronic device informs the ESTSM server computer system that it is operating normally 4065 and the electronic device transitions back into the registered and active state 4010.

Referring to FIG. 41, the states and transitions of an electronic device in ESTSM from a registered and active state to override state are shown. As described above, to continue using the electronic device if the Application component on the electronic device is unable to communicate with the ESTSM server computer system, the user must enter an activation password 4120. ESTSM on the electronic device is then bypassed in the override state 4130. If the electronic device is not reported stolen and the ESTSM Application component re-establishes communication with the ESTSM server computer system 4140, the electronic device returns back to the registered and active state 4110.

Referring to FIG. 42, the states and transitions of an electronic device in ESTSM for the “Data Destroy Service” is shown. As shown in FIG. 2 b, the user may select the “Data Destroy Service” that erases the electronic device harddisk drive. If the “Data Destroy Service” is selected, the electronic device registered and active 4210 with ESTSM may be reported stolen 4220 by the user. A stolen electronic device is placed into the reported stolen state 4230 and once the stolen device connects to the Internet 4240, it is placed into the being tracked state 4250. The user is sent a location identification email shown in FIG. 9 and because the user had selected the data destroy service is again given the option to select or bypass data destroy. If the user selects data destroy 4260, then the Application component on the electronic device erases the hard disk drive and the electronic device is in the erase harddisk state 4270.

Referring to FIG. 43, the states and transitions of an electronic device in which the corporate user of the device is removed from ESTSM is shown. As described above, a corporate user may have an electronic device which is registered and active 4310 with ESTSM. If ESTSM were not installed on the electronic device but rather the device was protected by a password known only to the user, the electronic device would be rendered unusable if the user left the organization. With ESTSM, if the corporate user leaves the organization 4320, the corporate administrator may remove the user's access rights to the ESTSM system. The electronic device used by the user is placed into the user removed state 4330.

If an electronic device is in the REPORTED STOLEN, BEING TRACKED or DISABLED state, the user can use a “System Recovered” interface that preferably may be a button to bring the electronic device back to the ACTIVE state. The procedure after the electronic device is recovered may be different depending on the ESTSM services selected for the recovered electronic device and the current state of the electronic device. In the preferred embodiment of the invention, the user may be required to fill out a recovery incident report, which documents the circumstances under which the electronic device was recovered.

The electronic device may be in the HALF-RECOVERED state when recovered, indicating that the electronic device is currently locked from boot access. The electronic device screen will show system information such as the manufacturer, model number and serial number of the electronic device and an unlock key. The electronic device screen will prompt the user to enter an activation password to re-enable boot access to the device. On the ESTSM website, after completing the recovery incident report, the user will be asked to enter the system information and unlock key indicated on the screen of the electronic device. The ESTSM server computer system will generate the activation password that the user can enter on the recovered electronic device to re-enable boot access.

From the ESTSM website, a user may also view the ESTSM services that are currently active on any of their electronic devices. The user may also add other ESTSM services and be billed accordingly. The user may also switch the options of certain services. For example, as shown in FIG. 2 a, the user may switch from “Track and Disable” option to “Continuous Track” option under the “Tracking Service.”

A user may be informed by the application component of new services that are available for ESTSM. Preferably, the application component may display a pop-up information message box that explains the new services along with pricing information. The application component may optionally allow the user to purchase the new service using an interface in the message box.

The user may also view billing information about their account. The billing information will show all charges to the user's credit card and the services which were purchased along with the date of purchase.

The ESTSM server computer system includes electronic device status logs that show all the ESTSM activity for an electronic device. The user may view the electronic device status logs. These logs may be used to see when an electronic device was reported stolen, a summary of the tracking location information collected for an electronic device, date and times of recovery or device disabling events, and any other device status information.

The ESTSM website may also be used to update user information, such as address, telephone number, email address, and so forth. Also, the user's billing information such as the credit card number and expiration date may also be updated.

The user may want to upgrade the operating system or hardware (specifically the hard disk drive) on the electronic device. As described above, the ESTSM BIOS ensures that the ESTSM application components may not be removed from the hard disk drive. Thus, if the user upgrades to a new hard disk drive, the user will be asked to insert the electronic device's recovery media. In the preferred embodiment of the invention, the recovery media may be a floppy diskette but in other embodiments the recovery media may be a Compact Disc-Read Only Memory (CD-ROM) or Universal Serial Bus (USB) key storage device. The ESTSM BIOS will prevent the system from booting until it detects the presence of the recovery media. The ESTSM BIOS component will automatically run a special program from the recovery media and this program will re-install all the ESTSM application components and special hidden partition on the hard disk drive (described in greater detail below). In some other embodiments of the invention where a specal hidden partition is not present, the user may load the ESTSM application components into the hard disk drive directly.

The user has to take no special action to upgrade the operating system on an electronic device that already has the ESTSM components properly installed and running. When the user upgrades the OS, the ESTSM application components will also be maintained as part of the OS upgrade. If the ESTSM components are removed inadvertently, the ESTSM BIOS component will automatically re-install the ESTSM application components from a special hidden partition that exists on the hard disk. This operation will be transparent to the user.

Turning now to FIG. 44, in the preferred embodiment of the invention, the ESTSM architecture consists of application components 4405, non-viewable component 4415 and a BIOS component 4410 that work together to provide a secure environment for electronic device operation. The application components may be files stored on a hard disk drive (HDD) 4400 of the electronic device and may include startup files 4420, ESTSM application 4425, and ESTSM Dynamic Link Libraries (DLL) 4430. A web browser application 4435 connectd to and capable of communicating with the ESTSM DLL 4430 may be present on the HDD. The application component runs within the operating system environment and is responsible for communicating with the ESTSM server computer system 4465 through the Internet 4475. Server computer system 4465 includes a number of servers 4470 a, 4470 b, . . . 4470 n that may be web servers containing the web pages and data for ESTSM described above. The application component 4405 determines from the ESTSM server computer system 4465 if the electronic device has been reported stolen, and if so, the application component takes the appropriate action based on the services the user registered for (i.e. disable electronic device, track location, erase hard disk drive, etc).

The BIOS component 4410 ensures that the application component 4405 can not be removed from the system or bypassed in any way. The BIOS component 4410 consists of a small piece of code that resides in the system BIOS ROM image located in a secure non-volatile area 4465. In some embodiments of the invention, a non-viewable component 4415 program VALIDATOR 4450 resides on a special hidden partition 4455 of the hard disk drive and is executed during Power-On-Self-Test (POST) of the electronic device. Every time the electronic device boots up, the BIOS component 4410 will check the integrity of the ESTSM non-viewable component 4415 and application component 4405 programs and files, and restore the original programs and files, if they have been tampered with. Furthermore, the BIOS component 4410 will ensure that the application component 4405 has run properly on the previous device boot and will take action if it is determined that an attempt to bypass the application component 4405 has occurred.

In some embodiments of the invention, the BIOS component 4410 consists of a BIOS ROM image that is integrated into the system BIOS. The non-viewable component 4415 consists of a VALIDATOR program 4450 which resides in a special hidden partition 4455 created by ESTSM. Together, the ROM image and VALIDATOR cooperate to make sure that someone cannot bypass or circumvent the ESTSM application component 4405 from running. This is done by the ESTSM BIOS in the three ways shown below. In this document, reference made to “ESTSM BIOS” may refer to the code in the BIOS ROM image or VALIDATOR or combination of both.

-   1. Validating the integrity of the ESTSM special hidden partition     4455 and VALIDATOR program 4450. The ESTSM hidden partition 4455     contains the VALIDATOR program 4450 and also contains a copy of the     original application component fileset 4445. If the ESTSM hidden     partition 4455 has been deleted from the electronic device's hard     disk drive 4400 or in some other way altered, the ESTSM BIOS ROM     image component will detect this and effectively force     re-installation of the partition 4455 and original fileset 4445 from     the recovery media 4460. This prevents someone from simply low level     formatting the hard disk drive, or just replacing the hard disk     drive with a new blank disk to bypass ESTSM. The ESTSM VALIDATOR     program 4450 can then “re-install” the ESTSM application component     4405 from the ESTSM Backup (Original) fileset 4445 on the special     hidden ESTSM partition 4455 of the hard disk drive 4400. -   2. Verifying that the application has been run on each boot. The     ESTSM BIOS implements a messaging protocol with the ESTSM     application components 4405 to ensure that the ESTSM application     components 4405 are run on every boot. This messaging protocol     utilizes the ESTSM Communications Area (ECA) 4440. In order to     bypass ESTSM, someone may delete key ESTSM application files in an     attempt to prevent the ESTSM application from running. Furthermore,     the thief may develop applications that will prevent ESTSM from     running on every boot even though it is correctly installed on the     electronic device's hard disk drive. The ESTSM application and BIOS     components work together to make sure that the ESTSM application     runs on every boot. If the ESTSM application component does not run     after the electronic device has booted, the ESTSM system will allow     the electronic device to boot a limited number of times and attempt     to run the ESTSM application component. If the ESTSM application     component does not run during any of these retries, the electronic     device will be prevented from booting after system POST. For devices     like PDA or Smart Phones this procedure is not required since the     application component is not removable or replaceable. -   3. Disabling a stolen electronic device reported as stolen so it may     not boot the operating system. If the ESTSM application component     4405 detects that the electronic device has been reported stolen, it     will inform the BIOS of the theft and freeze the system. If the     thief powers off the electronic device and attempts to boot the     system again, the ESTSM BIOS will prevent the system from booting     the operating system. If the electronic device is recovered and     returned to the original user, the user can “unlock” the device as     described above so it can boot.

In another embodiment of the invention as shown in FIG. 45, the architecture for an ESTSM enabled PDA, cell phone, or Smart Phone may include a Flash memory 4500 containing a changeable area 4510 and a system area 4520. The system area 4520 may include application components 4530 containing ESTSM application programs and a secure non-volatile area 4540 coupled to the application components 4530. In one embodiment of the invention, the system area 4520 may be non-viewable and implemented in non-volatile memory. The ESTSM enabled PDA, cell phone, or Smart Phone may continuously communicate to an ESTSM Server Computer System 4560 through an always-on Internet connection 4550 or other mobile device communication protocols such as SMS. Server computer system 4560 includes a number of servers 4570 a, 4570 b, . . . 4570 n that may be web servers containing the web pages and data for ESTSM described above.

In another embodiment of the invention as shown in FIG. 46, an ESTSM enabled electronic device may contain a HDD 4600 including an application component 4610 and an ECA 4620. Through an Internet connection 4690, the ECA 4620 allows the electronic device to communicate with the ESTSM Server Computer System 4685. Server computer system 4685 includes a number of servers 4685 a, 4685 b, . . . 4685 n that may be web servers containing the web pages and data for ESTSM described above. The HDD may include a Host Protected Area (HPA) 4630 containing ESTSM non-viewable components 4640. The non-viewable components 4640 may include a VALIDATOR program 4650 that inspects an ESTSM Communications Area (ECA) 4620 to determine if the ESTSM application components 4610 have run correctly during the last system boot. The non-viewable component may also contain a copy of the original application component software fileset 4660 if the files need to be re-installed to the HDD. As described above, every time the electronic device boots up, the BIOS component 4675 will check the integrity of the ESTSM non-viewable components 4640 and application component 4610 programs and files, and restore the original programs and files from the backup fileset 4660 or from recovery media 4670, if they have been tampered with. Furthermore, the BIOS component 4675 will ensure that the application component 4610 has run properly on the previous device boot and will take action if it is determined that an attempt to bypass the application component 4610 has occurred.

In another embodiment of the invention as shown in FIG. 47, the ESTSM enabled electronic device may include a HDD 4700 containing an application component 4710 that receives and transmits information to a remote component that may be an ESTSM WWW component 4725 through the Internet 4723. In some embodiments of the invention, the application component may reside in the ESTSM WWW component on the ESTSM website and may be installed by the user from the ESTSM website. The application component 4710 may be coupled to an ECA 4720. The ECA may couple to a BIOS component 4730 that is connected to a secure non-volatile area 4740 as described above. The ESTSM application component 4710 may communicate through the ECA 4720 to the BIOS component 4730. The ECA also allows the application and BIOS components to communicate with an ESTSM server computer system 4750 through an Internet connection 4770. Server computer system 4750 includes a number of servers 4760 a, 4760 b, . . . 4760 n that may be web servers containing the web pages and data for ESTSM described above.

Turning now to FIG. 48, in accordance with another embodiment of the invention, the architecture for an ESTSM enabled electronic device with SMS capability is shown. Preferably, the electronic device may include a Flash memory 4800 containing a changeable area 4810 that functions like non-volatile storage and may include a file system. A system area 4820 in the Flash memory 4800 that is non-changeable to a user of the electronic device may include an ESTSM SMS component 4830, ESTSM application component 4840 and a secure non-volatile area 4850 coupled to the application component 4850. The application component 4840 communicates with web servers 4870 a, 4870 b, . . . 4870 n in the ESTSM server computer system through an Internet connection 4845. The ESTSM server computer system also includes a SMS server 4860 coupled to the SMS component 4830 through a wireless communication connection 4855 such as Code Division Multiple Access (CDMA) or Global Mobile System (GSM). In some embodiments, the SMS component 4830 communicates with the ESTSM server using SMS services on the electronic device when an Internet connection is not available.

Turning now to FIG. 49, a computer system that includes a BIOS component, application component and non-viewable component in accordance with one embodiment of the invention is shown. Computer system 4900 may be configured in any number of ways, including as a laptop unit, a desktop unit, a network server, or any other configuration. Computer system 4900 generally includes a central processing unit (CPU) 4902 coupled to a main memory array 4906 and to a variety of other peripheral computer system components through an integrated bridge logic device 4904. The bridge logic device 4904 is sometimes referred to as a “North bridge” for no other reason than it often is depicted at the upper end of a computer system drawing. The CPU 4902 preferably couples to North bridge logic 4904 via a CPU bus 4908, or the bridge logic 4904 may be integrated into the CPU 4902. The CPU 4902 may comprise, for example, a Pentium™ IV microprocessor. It should be understood, however, that computer system 4900 could include other alternative types of microprocessors. Further, an embodiment of computer system 4900 may include a multiple-CPU architecture, with each processor coupled to the bridge logic unit 4904. An external cache memory unit 4909 further may couple to the CPU bus 4908 or directly to the CPU 4902.

The main memory array 4906 preferably couples to the bridge logic unit 4904 through a memory bus 4910. The main memory 4906 functions as the working memory for the CPU 4902 and generally includes a conventional memory device or array of memory devices in which program instructions and data are stored. The main memory array may comprise any suitable type of memory such as dynamic random access memory (DRAM) or any of the various types of DRAM devices such as synchronous DRAM (SDRAM), extended data output DRAM (EDO DRAM), or Rambus™ DRAM (RDRAM).

The North bridge 4904 couples the CPU 4902 and memory 4906 to the peripheral devices in the system through a Peripheral Component Interconnect (PCI) bus 112 or other expansion bus, such as an Extended Industry Standard Architecture (EISA) bus. The present invention, however, is not limited to any particular type of expansion bus, and thus various buses may be used, including a high speed (66 MHz or faster) PCI bus. Various peripheral devices that implement the PCI protocol may reside on the PCI bus 4912, as well.

The computer system 4900 preferably includes a graphics controller 4916 that couples to the bridge logic 4904 via an expansion bus 4914. As shown in FIG. 49, the expansion bus 4914 comprises an Advanced Graphics Port (AGP) bus. Alternatively, the graphics controller 4916 may couple to bridge logic 4904 through the PCI bus 4912. The graphics controller 4916 may embody a typical graphics accelerator generally known in the art to render three-dimensional data structures on display 4918.

Bridge logic 4904 includes a PCI interface to permit master cycles to be transmitted and received by bridge logic 4904. The bridge logic 4904 also includes an interface for initiating and receiving cycles to and from components on the AGP bus 4914. The display 4918 comprises any suitable electronic display device upon which an image or text can be represented. A suitable display device may include, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), a thin film transistor (TFT), a virtual retinal display (VRD), or any other type of suitable display device for a computer system.

The computer system 4900 optionally may include a Personal Computer Memory Card International Association (PCMCIA) drive 4932 coupled to the PCI bus 4912. The PCMCIA drive 4932 is accessible from the outside of the computer and accepts one or more expansion cards that are housed in special PCMCIA cards, enclosures which are approximately the size of credit cards but slightly thicker. Accordingly, PCMCIA ports are particularly useful in laptop computer systems, in which space is at a premium. A PCMCIA card typically includes one connector that attaches to the PCMCIA port 4932, and additional connectors may be included for attaching cables or other devices to the card outside of the computer 4900. Accordingly, various types of PCMCIA cards are available, including modem cards, network interface cards, bus controller cards, and memory expansion cards.

If other secondary expansion buses are provided in the computer system, another bridge logic device typically couples the PCI bus 4912 to that expansion bus. This bridge logic is sometimes referred to as a “South bridge,” reflecting its location vis—vis the North bridge in a typical computer system drawing. In FIG. 49, the South bridge 4922 couples the PCI bus 4912 to an Industry Standard Architecture (ISA) bus 4926 and to an Integrated Drive Electronics (IDE) bus 4964. The IDE bus 4964 typically interfaces input and output devices such as a CD ROM drive, a Digital Video Disc (DVD) drive, a hard disk drive, and one or more floppy disk drives. In accordance with the embodiment of the invention shown in FIG. 44, the IDE bus 4964 shown in FIG. 49 couples to HDD 4400. Preferably, ESTSM application component 4405 and ECA 4440 may be executable software files stored in a file system of HDD 4400. Hidden partition 4455 in HDD 4400 may include ESTSM non-viewable components 4415 as described in detail above with reference to FIG. 44.

Various ISA-compatible devices are shown coupled to the ISA bus 4926, including a BIOS ROM 4944. The BIOS ROM 4944 is a memory device that stores commands which instruct the computer how to perform basic functions such as sending video data to the display or accessing data on hard floppy disk drives. In addition, the BIOS ROM 4944 may be used to store power management instructions for hardware-based (or “legacy”) power management systems or to store register definitions for software-based power management systems. The BIOS instructions also enable the computer to load the operating system software program into main memory during system initialization and transfer control to the operating system so the operating system can start executing, also known as the INT19 “boot” sequence. BIOS ROM 4944 in FIG. 49 includes the ESTSM BIOS component 4410 in accordance with the embodiment of the invention shown in FIG. 44. The ESTSM BIOS component 4410 in BIOS ROM 4944 couples through a bus that may be a serial bus 4464 (a serial bus generally is a bus with only one data signal) to secure non-volatile area 4465 containing firmware code. The BIOS ROM 4944 typically is a “nonvolatile” memory device, which means that the memory contents remain intact even when the computer 4900 powers down. By contrast, the contents of the main memory 4906 typically are “volatile” and thus are lost when the computer shuts down.

The South bridge 4922 preferably supports an input/output (I/O) controller 4960 that operatively couples to basic input/output devices such as a keyboard 4968, a mouse 4970, a floppy disk drive 4966, general purpose parallel and serial ports 4972, and various input switches such as a power switch and a sleep switch (not shown). The I/O controller 4960 typically couples to the South bridge via a standard bus, shown as the ISA bus 4926 in FIG. 49. A serial bus 4962 may provide an additional connection between the I/O controller 4960 and South bridge 4922. The I/O controller 4960 typically includes an ISA bus interface (not specifically shown) and transmit and receive registers (not specifically shown) for exchanging data with the South bridge 122 over the serial bus 4962.

Turning now to FIG. 50, a wireless communication device that may be a PDA, cell phone or Smart Phone includes a changeable area and an application component in a system area in accordance with the embodiment of the invention of FIG. 45. The wireless communication device 5000 may transmit and receive information with a plurality of base transceiver stations (BTS) not shown in FIG. 50. Each BTS may transmit in a forward or downlink direction both physical and logical channels to the mobile station 5000 in accordance with a predetermined air interface standard. A reverse or uplink communication path also exists from the mobile station 5000 to the BTS, which conveys mobile originated access requests and traffic.

The air interface standard can conform to any suitable standard or protocol, and may enable both voice and data traffic, such as data traffic enabling Internet access and web page downloads. One suitable type of air interface is based on TDMA and may support a GSM or an advanced GSM protocol, although these teachings are not intended to be limited to TDMA or to GSM or GSM-related wireless systems. Another wireless system and air interface, such as a WCDMA system, may serve at least a part of the geographical area served by the wireless communication system shown in FIG. 50, and the mobile station 5000 maybe a multi-band terminal that is capable of operating with either the GSM or the WCDMA network.

The mobile station 5000 typically includes a microcontrol unit (MCU) 5020 having an output coupled to an input of a display 5040 and an input coupled to an output of a keyboard or keypad 5060. The mobile station 5000 may be contained within a card or module that is connected during use to another device. For example, the mobile station 5000 could be contained within a PCMCIA or similar type of card or module that is installed during use within a portable data processor, such as a laptop or notebook computer, or even a computer that is wearable by the user.

The MCU 5020 includes or is coupled to a memory 5030, including a system area 4520 for storing ESTSM application components 4530, as well as a changeable area for temporarily storing required data, scratchpad memory, received packet data, packet data to be transmitted, and the like. A separate, removable SIM (not shown) can be provided as well, the SIM storing, for example, a preferred Public Land Mobile Network (PLMN) list and other subscriber-related information. The system area 4520 may also store a program enabling the MCU 5020 to execute the software routines, layers and protocols required to operate in the wireless communications system, as well as to provide a suitable user interface (UI), via display 140 and keypad 160, with a user. Although not shown, a microphone and speaker are typically provided for enabling the user to conduct voice calls in a conventional manner.

The mobile station 5000 also contains a wireless section that includes a digital signal processor DSP 5080, or equivalent high speed processor or logic or control unit, as well as a wireless transceiver that includes a transmitter (Tx) 5010 and a receiver (Rx) 5020, both of which are coupled to an antenna 5040 for communication with the BTS 50. At least one local oscillator (LO) 5060, such as a frequency synthesizer, is provided for tuning the transceiver. Data, such as digitized voice and packet data, is transmitted and received through the antenna 5040.

As mentioned above with reference to FIG. 45, the ESTSM enabled PDA, cell phone, or Smart Phone may continuously communicate to the ESTSM Server Computer System through an always-on Internet connection. Valuable information such as telephone numbers, email addresses, calendar appointments, sales meetings and other daily reminders on a PDA, cell phone or Smart Phone with ESTSM can be retrieved from a stolen device in one embodiment of the invention by the user calling an ESTSM service center to report the device as stolen. Because the PDA, cell phone, or Smart Phone has an always-on Internet connection, valuable data on the device can be recovered and stored on the ESTSM server computer system as soon as the device is reported stolen. After recovery, the data may be erased off the stolen PDA, cell phone, or Smart Phone and the device disabled, making it worthless for the thief. Upon the ESTSM user purchasing a replacement PDA, cell phone or Smart Phone, the valuable data recovered and stored on the ESTSM server computer system from the user's stolen device can be placed on the user's new replacement device.

Turning now to FIG. 51, one embodiment of the ESTSM server computer system 5100 of FIGS. 44-47 is shown in more detail. Clients 5110 are ESTSM enabled electronic devices that transmit and receive information through firewall 5120 to web servers 5130. The firewall 5120 may be software executing on each of the web servers 5130 or a stand alone firewall device with dedicated hardware and software that may be a computer system. Web servers 5130 as described above include web pages for administration and use of ESTSM as well as software to transmit the web pages and receive responses from clients 5110. Web servers 5130 connect through firewall 5140 to one or more database servers 5150. Firewall 5140 may be software executing on each of the database servers 5150 or a stand alone firewall device with dedicated hardware and software that may be a computer system. Database servers 5150 may contain among other information, user configuration information and access rights for clients 5110. Configuration information may include the ESTSM services selected by a user, the electronic devices associated with a particular user, electronic device identification information, billing information such as credit card number and expiration date, electronic device location and status logs, and so forth. Web servers 5130 may also couple to File Transfer Protocol (FTP) server 5160 that allows clients 5110 to download large files directly without having to go through web servers 5130. Web servers 5130 also have access to files on FTP server 5160 allowing clients to access and view the contents of these files through the web servers.

Turning now to FIG. 52, web servers 5130 of FIG. 51 are depicted in greater detail and show connections between the primary and secondary servers in accordance with the preferred embodiment of the invention. Clients 5110 may each connect to primary server 5210 and each of secondary server 5220 a, 5220 b, . . . and 5220 n. The primary server 5210 and secondary servers 5220 a, 5220 b, . . . 5220 n are coupled to each other and can communicate and transfer information. In some embodiments of the invention as described in greater detail below, each of clients 5110 includes an application component that works with web browser software such as Microsoft® Interney® Explorer® to ensure that if Explorer® can access the ESTSM website, the ESTSM application components will also be able to access the website. If Explorer® on the client can not get to the ESTSM website on the primary server 5210, it will then try to access the ESTSM secondary servers 5220 a, 5220 b, . . . 5220 n for status of the primary. If the secondary servers are also unavailable, but ESTSM application component on the client can access other popular websites, then it is assumed that some firewall or other software has been loaded to attempt to block ESTSM operation.

The web pages for registration on the ESTSM server can be customized for each type of electronic device and manufacturer. This way, manufacturers can offer different services to the user, during the registration phase, based on the model and target customers for that model. Thus, for example, a manufacturer may want to set a higher price for “Data Destroy Services” on corporate laptop models, then on consumer laptop models.

If the ESTSM server computer system receives a message from an electronic device that has been reported stolen, and the “Tracking Service” is registered for that electronic device, the ESTSM server will log the IP address of the stolen electronic device. The ESTSM server computer system will get the IP address from the header of the message packet (part of Internet Protocol (IP)) and will not have to execute a tracing program such as TraceRoute on the electronic device that may be a client personal computer. The ESTSM server will use the Internet to lookup the information for that IP address and will send the tracking location email as described above to the user.

The ESTSM server computer system hosts all the web pages that provide the user experience once logged into the, ESTSM website. The ESTSM server environment can be duplicated at a corporate customer facility and the specific serial numbers of the electronic devices at that corporation can be re-directed to work directly with the ESTSM server located at that corporation. Thus, corporate customers, for security purposes, can control the flow of messages to servers located at their own facility.

If the ESTSM server needs repairs to hardware, new software, functional changes to webpages, etc. electronic device clients may be requested by the server to stop making new queries to the server for a random amount of time. Thus, needed updates and repairs to the ESTSM sever may be performed during this time.

Turning now to FIG. 53, a flow diagram in accordance with some embodiments of the invention of the BIOS component of ESTSM of FIG. 44 is shown. The Power on Self Test (POST) firmware may call the ESTSM BIOS component 5310 towards end of POST. The BIOS component will first check to see if the electronic device has already been disabled by ESTSM 5335 (i.e. the electronic device was reported stolen, or some other ESTSM failure occurred). If the electronic device is already disabled, the BIOS component will display the system information and a boot specific unlock key and will prompt the user to enter the activation password to re-enable system boot 5320. This activation password can be obtained by the original user through the ESTSM website or by calling the monitoring station.

If the system was not already disabled, the BIOS component checks to see if the special ESTSM hidden partition exists 5340. If it does exist, the BIOS component will transfer control to ESTSM non-viewable component VALIDATOR program 5345. If the hidden partiiton does not exist the BIOS component will create the ESTSM hidden partition 5350. If there is a bootable operating system partition on the hard disk 5355, the BIOS component will force the user to insert the recovery media into the appropriate device 5365. The BIOS component will re-build the ESTSM hidden partition using the files from the recovery media 5370. As mentioned above, if the hidden partition does not exist, a check is also made to see if a bootable operating system partition is present before forcing the recovery media to be inserted. If a bootable operating system partition is not present, then the electronic device will proceed with the boot process 5360 until it stops because no bootable OS is present. This may occur if the thief deletes the OS in which case he must install the OS and the recovery media to allow the system to reboot. Alternatively, a bootable OS partition may not be present as during initial HDD installation at the factory, and a master hard disk image may be used for seamless factory installation during boot process 5360 without requiring the recovery Media to be inserted in each electronic device during manufacture.

Turning now to FIG. 54, a flow diagram of the VALIDATOR program in the non-viewable component of the ESTSM in accordance with some preferred embodiments of the invention is shown. If the hidden partition on the hard disk is valid, the BIOS component will load and transfer control to the VALIDATOR program 5345 on the hidden partition as shown in FIG. 53 and described above. The VALIDATOR program inspects the ESTSM Communications Area (ECA) to determine if the ESTSM application components have run correctly during the last system boot 5410. If the ECA information is correct (i.e. ESTSM application was run correctly), then the VALIDATOR program will return control to POST to proceed with INT19 OS boot process 5430. If the VALIDATOR program determines that the application components failed to run correctly 5420, the user is warned to correct the problem otherwise the electronic device will be disabled within a number of system boots 5440 that in the preferred embodiment of the invention is 5 system boots. The VALIDATOR program will then restore the ESTSM application components from ESTSM backup fileset to try to correct the problem 5450. If the number of system boots has been reached and ECA information is still not correct 5460, then ESTSM will disable the system 5470. The procedure described above may then be used to re-enable the system. An application component failure will be generated if the thief deletes or tampers with ESTSM files, loads an application or service to try to bypass ESTSM operation, or in any other way tries to prevent ESTSM from running. After the VALIDATOR program has completed operation, it returns control back to the electronic device BIOS 5430 so that system POST may be completed and the normal OS boot can occur via the INT19 interface.

In some other embodiments of the invention, the check of the ECA to determine if the ESTSM application components have run correctly is performed by the BIOS component-thus the VALIDATOR program may be located in the BIOS component. If the VALIDATOR program determines that the application components failed to run correctly, the user is asked to install the application components onto the electronic device.

As shown in FIG. 44, the ESTSM application component consists of two sets of programs: (1) ESTSM application program and (2) startup program files. The application component programs work together to provide the ESTSM environment described above and periodically check with the ESTSM server computer system to see if the electronic device is reported stolen and take the appropriate action.

A flow diagram of the application component of the ESTSM is shown in FIG. 55 in accordance with the preferred embodiment of the invention. The startup program 5500 creates the appropriate system processes and loads and executes the ESTSM application program 5505 on the electronic device that performs most of the ESTSM operations. The ESTSM application program works with the operating system driver files to communicate with the ECA. The ESTSM application program will check the integrity of all the ESTSM application components 5510 and will ensure ESTSM is working correctly. The ESTSM application program will communicate this information to the BIOS component through the ECA. Checking the integrity of ESTSM application components may include interfacing with specialized security hardware on the electronic device that in one preferred embodiment of the invention may be Trusted Platform Module (TPM) integrated circuitry. If there is a problem with the ESTSM application components, no information will be communicated to the ECA and oh the next electronic device boot, the BIOS component will not allow the electronic device to boot. Otherwise, the ESTSM application program will then try to detect an Internet connection on the electronic device. Once an Internet connection is established by the user, the ESTSM application program will attempt to contact the primary ESTSM server 5515. If the ESTSM application program is successful in contacting the primary ESTSM server, the application program will then send an encrypted query to the primary ESTSM server 5520. Preferably, encryption of the query may involve interfacing with specialized security hardware on the electronic device such as TPM integrated circuitry described in more detail below. This query will identify the electronic device by the device system information such as serial number and model number (no other user data is sent to the server) 5520. The ESTSM application program receives the electronic device status from the server to determine if the device is registered with ESTSM 5525. If the electronic device is not registered with the ESTSM server, the user is given the option to complete the registration phase as described above and shown in FIG. 55 5535, 5540, and 5545.

If the system is registered with ESTSM server, the electronic device executing the ESTSM application program will receive a response from the ESTSM server computer system indicating whether or not the electronic device is reported stolen. If the electronic device is in an active state (i.e. not stolen), the application program will wait an interval and again contact the ESTSM server 5515. If the electronic device is reported stolen 5550, the ESTSM application program will cooperate with the other application components to take the appropriate action (i.e. disable the system, erase the hard disk drive, etc) 5555 and 5560. If the user has selected the disable electronic device service, then the ESTSM application program will inform the ECA of electronic device disabled state 5580 and freeze the electronic device 5585. The electronic device executing the ESTSM application program will send an encrypted message to the ESTSM server periodically while the system is connected to the Internet.

The application component of ESTSM is designed so that firewall software can not block the ESTSM application components from accessing the ESTSM website. If firewall software could block the ESTSM application components, a thief could merely install the firewall software to bypass ESTSM. The ESTSM application program works with web browser software such as Microsoft® Internet® Explorer® to ensure that if Explorer® can access the ESTSM website, the ESTSM application components will also be able to access the website. If Explorer® can not get to the ESTSM website on the primary server, it will then try to access the ESTSM secondary servers for status of the primary as shown in FIG. 55 in 5565. If the secondary servers are also unavailable, but ESTSM can access other popular websites 5587, then it is assumed that some firewall or other software has been loaded to attempt to block ESTSM operation. In this case, in one preferred embodiment of the invention, the user is warned that they must correct the problem 5570 within five boots 5575 or enter an “override” code to continue operation with ESTSM temporarily disabled. The “override” code can be obtained from the ESTSM website, call center, or an automated response system. If the override code is not entered, the system will be disabled after five boots 5580 and 5585, and the user must get the activation password as described above.

The ESTSM server is located at a particular address on the WWW accessible to the user. The application components of ESTSM communicate with this web server during the registration phase and periodically once the system is registered to determine if the electronic device has been reported stolen.

Turning now to FIG. 56, encryption and encoding of information by the client electronic device and decoding and decryption of information by the server computer system in accordance with one preferred embodiment of the invention is shown. A client 5610 that is an ESTSM enabled electronic device includes an ESTSM application component 5615 as described above. The ESTSM application component 5615 may be coupled to an encryption/decryption module 5620 that transmits and receives encrypted and encoded data. The encrypted and encoded data may be transmit and received from an ESTSM server computer system 5630 through a communication medium 5625 such as HyperText Tranfer Protocol (HTTP). The server computer system 5630 includes an ESTSM server application 5640 that may include web pages and information displayable on ESTSM enabled devices as described above and ESTSM server application software. The ESTSM server application 5640 may be coupled to an encryption/decryption module 5635 that transmits and receives encrypted and encoded data to and from client 5610.

Turning now to FIG. 57, encryption and encoding of information by the client electronic device and decoding and decryption of information by the server computer system of FIG. 56 is shown. Client electronic device 5610 may frequently and at randomly selected times send a query to server computer system 5630 asking if the electronic device has been reported stolen. The query is encrypted 5715 by encryption/decryption module 5620 using an encryption technique as described below into a binary format sequence 5720 of ones and zeroes. The sequence of ones and zeros is encoded 5725 by encryption/decryption module 5620 using an encoding technique as described below into an American Standard Code of Information Interchange (ASCII) text format 5730. ASCII text format is a standard 7-bit ASCII character code embedded in an 8 bit byte whose high order bit is always zero as described in ANSI standard X3.64, herein incorporated by reference.

Simultaneously with the encryption and encoding performed by encryption/decryption module 5620, the server computer system receives ASCII text formatted data 5755 via communication medium 5625. The ASCII text formatted data is decoded 5750 by encryption/decryption module 5635 using a decoding technique as described below into a binary format sequence 5745 of ones and zeroes. The sequence of ones and zeroes is decrypted 5740 by encryption/decryption module 5635 into query information 5735 that may be as mentioned above asking if the electronic device has been reported stolen.

Referring now to FIG. 58, a flow diagram implemented in the client and server for encoding binary format sequence data into ASCII text format data in accordance with the preferred embodiment of the invention is shown. If the end of the binary format sequence data source 5810 has been reached as determined by the value of the source_length variable then encoding ends 5815. If the end has not been reached, then the next byte to encode is stored 5820 in a variable. Next, ‘n’ bits from the variable are extracted 5820 into another variable that in one preferred embodiment may be C1. ASCII text format may have n=6 bits with the highest order 7^(th) and 8^(th) bit always zero. Variable C1 is passed to ENC( ) function that performs binary mapping operations on the binary sequence data to generate an encoded byte 5830. The encoded byte is placed into a Destination data structure 5840 that may be an array of bytes for transmission over communication medium 5625. The encoded byte is re-initialized to a zero value in the preferred embodiment of the invention and the source_length variable is decremented.

Referring now to FIG. 59, a flow diagram implemented in the client and server for decoding ASCII text format data into binary data in Accordance with the preferred embodiment of the invention is shown. Encryption/decryption modules located in the client electronic device or server computer system receive encoded bytes of ASCII text format data that are placed into a data structure that may be an array of bytes. The data structure is described by a source_length variable that indicates the number of ASCII text format data bytes present in the array. Every time a new byte of data is received by the encryption/decryption module and placed in the array, the source_length variable is incremented and when a byte of data is removed and decoded the source_length variable is decremented. If the end of source 5910 has been reached, the array will become empty and decoding will end 5930. If the end of the source has not been reached, then, preferably, a current ASCII text format byte of data is placed into variable E. The ASCII text format byte of data in variable E is passed to DECODE( ) function that performs mapping operations on the data to generate a decoded byte ED 5950. The lower six bits of the decoded byte ED are placed into a Destination data structure 5960 that may be an array of bytes received over communication medium 5625. Finally, the source_length variable is decremented as described above.

Turning now to FIG. 60, a flow diagram showing encryption and encoding of SMS messages from SMS server to SMS enabled ESTSM electronic device for the system of FIG. 48 is depicted. Each SMS capable device that in some embodiments of the invention may be a Smart phone includes unique device information that is used in the encoding and encryption process. The encryption/decryption module in the Smart phone stores the device information into a variable DI as shown in block 6010. The encryption/decryption module passes the device information in variable DI to a function Jumble( ) as shown in block 6020 and stores the result into a variable JDI. In some embodiments of the invention, the function Jumble( ) rearranges and reorders the individual bytes in variable DI. Next, the encryption/decryption module as shown in block 6030 generates an encrypted command by passing the jumbled device information in variable JDI and an ESTSM Secret Cmd to function FN. The ESTSM Secret Cmd is a command sent from the ESTSM server to the electronic device for a function supported by the ESTSM device. The function FN returns an encrypted command that is stored in variable ECMD and may be an array of bytes. Next, in block 6040, the encryption/decryption module calls the Encode function that may be the flowchart shown in FIG. 58. The Encode function is passed the variable ECMD containing the encrypted command and encodes the array of bytes as shown in FIG. 58. The encoded array of bytes is stored in a variable EncECMD that is transmitted to the ESTSM server computer system over the communication medium 5625.

Turning now to FIG. 61, a flow diagram showing decoding and decryption of SMS messages is depicted

Implementing ESTSM on an electronic device may require the manufacturer to integrate the ESTSM BIOS components including the BIOS ROM images into the system BIOS of the electronic device. This is the only task that may have to be performed during the system's development phase. The integration of the ESTSM BIOS component requires very little effort. The ESTSM BIOS component is designed to minimize the effort required to integrate with the existing electronic device BIOS. Factors, such as size of code, complexity of integration, and so forth, have been addressed in the design of the ESTSM BIOS component. In one preferred embodiment of the invention as shown in FIG. 62 a, the ESTSM BIOS component is integrated with the existing electronic device BIOS using the technique described below.

-   -   1. Place the ESTSM BIOS component image files into a system BIOS         build file 6200. Preferably, the electronic device BIOS has 16         Kilobytes of free space to integrate the BIOS component image         files.     -   2. Build a data structure including the electronic device's         system information, programs to save and restore ESTSM critical         information in the Secure Non-volatile Area, and an optional         recovery media read function pointer and pass the address of         this data structure to an ESTSM BIOS image entry point in the         BIOS build file as shown in block 6210. Also ensure that the         Random Access Memory (RAM) areas that ESTSM uses are not used by         other BIOS functions. After the ESTSM BIOS image files are         integrated into the system BIOS build, the system BIOS code         builds the data structure as described above. The ESTSM BIOS         image may need a pointer to the function in the system BIOS that         reads from the recovery media. Since modern day BIOSes support         reading from almost all types of recovery media (i.e. floppy         diskettes, CD-ROM, USB key, and so forth), no extra code         development is required and the address of the read function         needs to be placed in the data structure passed to the ESTSM         BIOS image. In some alternative embodiments of the invention         that do not use recovery media, a pointer to the recovery media         read function in system BIOS is not needed. The electronic         device system BIOS developer should make sure that the RAM         address locations used by ESTSM are not used by the system BIOS.     -   3. As shown in block 6220, system BIOS needs to call the ESTSM         BIOS image entry point just before the INT19 bootstrap call. The         system BIOS calls the ESTSM BIOS image entry point before making         the INT19 boot strap call. At this point, the ESTSM BIOS image         will be invoked and will perform all the checks that enable the         secure system environment of ESTSM.

FIG. 62 b is an exemplary flow diagram showing integration of the ESTSM option ROM into a Phoenix® BIOS binary image.

In another embodiment of the invention, the ESTSM BIOS component is provided to the manufacturer of the electronic device in an encapsulated Option ROM image format that preferably may be ESTSM.ROM as shown in FIGS. 63 and 64. In some preferred embodiments of the invention as shown in FIG. 63, the manufacturer may utilize tools provided by BIOS vendors such as BIOS editors 6300 to merge the encapsulated ROM ESTSM image into the manufacturer's base BIOS image using the Option ROM format 6310. In some other preferred embodiments of the invention as shown in FIG. 64, the manufacturer may use a BIOS Configuration Utility 6400 to insert the encapsulated ROM ESTSM image 6410 into the manufacturer's base BIOS ROM image 6420. In this embodiment, the BIOS calls the ESTSM Option ROM in the same way as it would any other Option ROM image. The ESTSM ROM proceeds in the same manner as it would if it had been integrated into the BIOS using known BIOS integration techniques by checking the system security during INT 19 boot strap call.

Returning now to FIG. 62 a, maintaining and updating of the electronic device system BIOS is minimized because of the design of the ESTSM BIOS component. When the manufacturer needs to do a system BIOS update for the electronic device, no changes need to be made to the ESTSM BIOS component in the system BIOS. The manufacturer can simply fix the bugs in the BIOS and do a new system BIOS build as shown in FIG. 62 a (which will include the ESTSM BIOS components) and the new system BIOS will work correctly. The new system BIOS can then be Flash upgraded by the user without any impact to ESTSM operation.

If an update is released for the ESTSM components, the updated versions of the BIOS component image files may be copied into the BIOS build file and a new build performed. Once the new build is complete, the updated system BIOS can be released to the user. No additional coding or maintenance tasks need to be performed to update the ESTSM BIOS components in the system BIOS.

Integration of the ESTSM application component requires no action by the manufacturer of the electronic device. This is because the ESTSM BIOS component restores the application components onto the hard disk drive of the electronic device once the OS is installed on the electronic device. In some other embodiments of the invention, the application component may be installed by the user of the electronic device as described above.

For some embodiments of the invention, creation of the ESTSM hidden partition may be performed immediately after installation of the electronic device's hard disk drive. Various utilities can be used to create the hidden partition. In one embodiment, a scripted installation program including the utility to create the hidden partition may be run at the beginning of the manufacturing process. Typically, this utility should be run just before the FDISK.EXE or some other utility is used to create the OS partition on the hard disk drive.

If the manufacturing process copies a prepared hard disk image directly to a blank hard disk, then the prepared image should be created with the ESTSM hidden partition installed. This way, when the prepared image is copied to the blank hard disk drive during manufacture, the ESTSM hidden partition will also be copied automatically from the prepared image.

Engineering and electronic device quality assurance test processes may be performed by the manufacturer providing the ESTSM monitoring station with a block of electronic device serial numbers to be used as part of the testing process. The monitoring station will mark these serial numbers as “test” in the ESTSM server computer system and the user will not be billed on the credit card for these systems. This will facilitate the test process at the manufacturer's facilities.

Turning now to FIG. 71, a flow diagram showing implementation of ESTSM on mobile devices that have SMS capability such as cellular telephones and Smartphones is depicted. In some embodiments of the invention, the ESTSM server computer system may inform the mobile device that it has been reported stolen and backup the data on the device. In some other embodiments of the invention, the ESTSM server may periodically backup the data on the device even if the mobile device has not been reported stolen. The ESTSM server may disable the mobile device (i.e. lock the user out but device can still communicate with ESTSM server) if the Subscriber Identity Module (SIM) card has been changed and the mobile device is reported stolen. The ESTSM server may also disable the mobile device if the International Mobile Equipment Identifier (IMEI) number has been changed and the device is reported stolen.

FIG. 72 shows the state transitions of a mobile device that has SMS capability for activation and operation of ESTSM services. If the user of the ESTSM system has selected the data service, the ESTSM server will recover the data requested by the user. Thus, if during ESTSM registration for the mobile device the user had selected only recovery of contacts and calendar data, these items will be backed-up. In some embodiments of the invention, the user may specify other data for recovery such as Mobile Commerce (M-commerce) related monetary value information stored on the mobile device. The recovered data may then be downloaded to the mobile device once it is found or a newly activated mobile device.

While the invention has been disclosed with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of the invention. 

1. An electronic device security and tracking system, comprising: a non-viewable component; an application component connected to the non-viewable component, said application component capable of communicating with the non-viewable component; a BIOS component connected to the non-viewable component; and, a server system capable of communicating through a secure medium with the application component.
 2. The electronic device security and tracking system of claim 1, wherein the server system is capable of communicating through the secure medium with the non-viewable component.
 3. The electronic device security and tracking system of claim 1, wherein the server system is capable of communicating through the secure medium with the BIOS component.
 4. The electronic device security and tracking system of claim 1, wherein the non-viewable component comprises: a fileset; and, a validator module connected to the fileset, said validator module capable of determining if the application component is present and has been tampered with.
 5. The electronic device security and tracking system of claim 1, wherein the non-viewable component is located in a hidden partition of a hard disk drive.
 6. The electronic device security and tracking system of claim 1, wherein the application component comprises: a plurality of startup files; an application file connected to the startup files, said application file capable of communicating with the startup files; and, a dynamic link library connected to the application file.
 7. The electronic device security and tracking system of claim 1, further comprising a secure area coupled to the BIOS component.
 8. The electronic device security and tracking system of claim 7, further comprising a recovery media receptacle coupled to the BIOS component, said receptacle capable of holding a recovery media.
 9. The electronic device security and tracking system of claim 1, wherein the application component communicates with the non-viewable component through a communications area.
 10. The electronic device security and tracking system of claim 1, wherein the application component is located on a hard disk drive.
 11. The electronic device security and tracking system of claim 10, wherein the BIOS component is located external to the hard disk drive.
 12. The electronic device security and tracking system of claim 1, wherein the BIOS component is capable of determining if the non-viewable component is present and has been tampered with.
 13. An electronic device security and tracking system, comprising: a nonvolatile storage device; a changeable area in the nonvolatile storage device, wherein the changeable area further comprises an application component and a secure area coupled to the application component; and, a server system capable of communicating through a secure medium with the application component.
 14. The electronic device security and tracking system of claim 13, wherein the server system is capable of communicating through the secure medium with the secure area.
 15. The electronic device security and tracking system of claim 13, wherein the electronic device is a personal digital assistant.
 16. The electronic device security and tracking system of claim 13, wherein the nonvolatile storage device is a Flash memory.
 17. The electronic device security and tracking system of claim 13, wherein the application component comprises an application file.
 18. An electronic device security and tracking system, comprising: a nonvolatile storage device; a changeable area in the nonvolatile storage device, wherein the changeable area further comprises a system area in the nonvolatile storage device, said system area comprising an application component and a secure area coupled to the application component; and a server system capable of communicating through a secure medium with the application component.
 19. The electronic device security and tracking system of claim 18, wherein the server system is capable of communicating through the secure medium with the secure area.
 20. The electronic device security and tracking system of claim 19, wherein the system area is not modifiable by a user of the electronic device.
 21. The electronic device security and tracking system of claim 18, wherein the electronic device is a personal digital assistant.
 22. The electronic device security and tracking system of claim 18, wherein the nonvolatile storage device is a Flash memory.
 23. The electronic device security and tracking system of claim 18, wherein the application component comprises an application file.
 24. An electronic device security and tracking system, comprising: a non-viewable component; an application component connected to the non-viewable component, wherein the application component comprises an application file, said application file capable of communicating with the non-viewable component; a BIOS component connected to the non-viewable component; and, a server system capable of communicating through a secure medium with the application file.
 25. The electronic device security and tracking system of claim 24, wherein the server system is capable of communicating through the secure medium with the non-viewable component.
 26. The electronic device security and tracking system of claim 24, wherein the server system is capable of communicating through the secure medium with the BIOS component.
 27. The electronic device security and tracking system of claim 24, wherein the non-viewable component comprises: a fileset; and, a validator module connected to the fileset, said validator module capable of determining if the application file is present and has been tampered with.
 28. The electronic device security and tracking system of claim 24, wherein the non-viewable component is located in a host protected area of a hard disk drive.
 29. The electronic device security and tracking system of claim 24, further comprising a secure area coupled to the BIOS component.
 30. The electronic device security and tracking system of claim 29, further comprising a recovery media receptacle coupled to the BIOS component, said receptacle capable of holding a recovery media.
 31. The electronic device security and tracking system of claim 24, wherein the application file communicates with the non-viewable component through a communications area.
 32. The electronic device security and tracking system of claim 24, wherein the application file is located on a hard disk drive.
 33. The electronic device security and tracking system of claim 32, wherein the BIOS component is located external to the hard disk drive.
 34. The electronic device security and tracking system of claim 24, wherein the BIOS component is capable of determining if the non-viewable component is present and has been tampered with.
 35. An electronic device security and tracking system, comprising: a remote component; an application component connected to the remote component, wherein the application component is capable of communicating with the remote component through a communication medium; a BIOS component connected to the application component; and, a server system capable of communicating through a secure medium with the application component.
 36. The electronic device security and tracking system of claim 35, wherein the server system is capable of communicating through the secure medium with the remote component.
 37. The electronic device security and tracking system of claim 35, wherein the server system is capable of communicating through the secure medium with the BIOS component.
 38. The electronic device security and tracking system of claim 35, wherein the remote component comprises a fileset.
 39. The electronic device security and tracking system of claim 35, wherein the application component comprises: a plurality of startup files; an application file connected to the startup files, wherein the application file is capable of communicating with the startup files; and, a dynamic link library connected to the application file.
 40. The electronic device security and tracking system of claim 35, further comprising a secure area coupled to the BIOS component.
 41. The electronic device security and tracking system of claim 35, wherein the application component communicates with the BIOS component through a communications area.
 42. The electronic device security and tracking system of claim 35, wherein the application component is located on a hard disk drive.
 43. The electronic device security and tracking system of claim 35, wherein the remote component is a world wide web component.
 44. The electronic device security and tracking system of claim 35, wherein the communication medium is Internet.
 45. The electronic device security and tracking system of claim 35, wherein the application component is located on a hard disk drive.
 46. The electronic device security and tracking system of claim 45, wherein the BIOS component is located external to the hard disk drive.
 47. The electronic device security and tracking system of claim 35, wherein the BIOS component is capable of determining if the application component is present and has been tampered with.
 48. An electronic device security and tracking system, comprising: a nonvolatile storage device; a changeable area in the nonvolatile storage device, wherein the changeable area further comprises an application component and a communication protocol component coupled to the application component; and, one or more servers capable of communicating through a secure medium with the application component.
 49. The electronic device security and tracking system of claim 48, wherein the communication protocol component is a smart messaging service component for mobile devices.
 50. The electronic device security and tracking system of claim 49, further comprising: one or more smart messaging service servers capable of communicating through a communications medium with the smart messaging service component; and, wherein the one or more servers that communicate with the application component are web servers.
 51. The electronic device security and tracking system of claim 50, wherein the communications medium is from the group consisting essentially of smart messaging service wireless link, Code Division Multiple Access, and Global Mobile System.
 52. The electronic device security and tracking system of claim 49, wherein the electronic device is from the group consisting essentially of Smart phone, smart messaging service capable device, and mobile phone device.
 53. The electronic device security and tracking system of claim 48, wherein the nonvolatile storage device is a Flash memory.
 54. The electronic device security and tracking system of claim 48, wherein the application component comprises an application file.
 55. An electronic device security and tracking system, comprising: a nonvolatile storage device; a changeable area in the nonvolatile storage device, wherein the changeable area further comprises a system area in the nonvolatile storage device, said system area comprising an application component and a communication protocol component coupled to the application component; and, one or more servers capable of communicating through a secure medium with the application component.
 56. The electronic device security and tracking system of claim 55, wherein the communication protocol component is a smart messaging service component for mobile devices.
 57. The electronic device security and tracking system of claim 56, further comprising: one or more smart messaging service servers capable of communicating through a communications medium with the smart messaging service component; and, wherein the one or more servers that communicate with the application component are web servers.
 58. The electronic device security and tracking system of claim 57, wherein the communications medium is from the group consisting essentially of smart messaging service wireless link, Code Division Multiple Access, and Global Mobile System.
 59. The electronic device security and tracking system of claim 56, wherein the electronic device is from the group consisting essentially of Smart phone, smart messaging service capable device, and mobile phone device.
 60. The electronic device security and tracking system of claim 55, wherein the nonvolatile storage device is a Flash memory.
 61. The electronic device security and tracking system of claim 55, wherein the system area is not modifiable by a user of the electronic device.
 62. The electronic device security and tracking system of claim 55, wherein the application component comprises an application file.
 63. A computer system, comprising: a central processing unit; a memory array coupled to said central processing unit; an expansion bus coupled to said central processing unit and said memory array, said expansion bus capable of interfacing peripheral devices; a BIOS memory coupled to said expansion bus, comprising: a BIOS component; a hard disk drive coupled to said expansion bus, comprising: a non-viewable component; an application component connected to the non-viewable component, said application component capable of communicating with the non-viewable component; and one or more servers capable of communicating through a secure medium with the application component.
 64. The computer system of claim 63, wherein the server system is capable of communicating through the secure medium with the non-viewable component.
 65. The computer system of claim 63, wherein the server system is capable of communicating through the secure medium with the BIOS component.
 66. The computer system of claim 63, wherein the non-viewable component comprises: a fileset; and, a validator module connected to the fileset, said validator module capable of determining if the application component is present and not been tampered with.
 67. The computer system of claim 63, wherein the non-viewable component is located in a hidden partition of the hard disk drive.
 68. The computer system of claim 63, wherein the BIOS memory is from the group consisting essentially of read-only-memory, electronically erasable read-only-memory, and Flash read-only-memory.
 69. The computer system of claim 63, wherein the application component comprises: a plurality of startup files; an application file connected to the startup files, said application file capable of communicating with the startup files; and, a dynamic link library connected to the application file.
 70. The computer system of claim 63, further comprising a secure area coupled to the BIOS component.
 71. The computer system of claim 70, further comprising a recovery media receptacle coupled to the BIOS component, said receptacle capable of holding a recovery media.
 72. The computer system of claim 63, wherein the application component communicates with the non-viewable component through a communications area.
 73. The computer system of claim 63, wherein the BIOS component is capable of determining if the non-viewable component is present and has not been tampered with.
 74. A computer system, comprising: a central processing unit; a memory array coupled to said central processing unit; an expansion bus coupled to said central processing unit and said memory array, said expansion bus capable of interfacing peripheral devices; a BIOS memory coupled to said expansion bus, comprising: a BIOS component; a hard disk drive coupled to said expansion bus, comprising: a non-viewable component; an application component connected to the non-viewable component, wherein the application component comprises an application file, said application file capable of communicating with the non-viewable component; and one or more servers capable of communicating through a secure medium with the application file.
 75. The computer system of claim 74, wherein the one or more servers are capable of communicating through the secure medium with the non-viewable component.
 76. The computer system of claim 74, wherein the one or more servers are capable of communicating through the secure medium with the BIOS component.
 77. The computer system of claim 74, wherein the non-viewable component comprises: a fileset; and, a validator module connected to the fileset, said validator module capable of determining if the application file is present and not been tampered with.
 78. The computer system of claim 74, wherein the non-viewable component is located in a host protected area of the hard disk drive.
 79. The computer system of claim 74, wherein the BIOS memory is from the group consisting essentially of read-only-memory, electronically erasable read-only-memory, and Flash read-only-memory.
 80. The computer system of claim 74, further comprising a secure area coupled to the BIOS component.
 81. The computer system of claim 80, further comprising a recovery media receptacle coupled to the BIOS component, said receptacle capable of holding a recovery media.
 82. The computer system of claim 74, wherein the application file communicates with the non-viewable component through a communications area.
 83. The computer system of claim 74, wherein the BIOS component is capable of determining if the non-viewable component is present and has not been tampered with.
 84. A communication system, comprising: a communication device, comprising: a controller unit; a digital signal processor coupled to the controller unit; a nonvolatile storage device coupled to the controller unit, comprising: a changeable area, wherein the changeable area further comprises an application component and a secure area coupled to the application component; and a server system capable of communicating through a secure medium with the application component.
 85. The communication system of claim 84, wherein the server system is capable of communicating through the secure medium with the secure area.
 86. The communication system of claim 84, wherein the communication device is a personal digital assistant.
 87. The communication system of claim 84, wherein the nonvolatile storage device is a Flash memory.
 88. The communication system of claim 84, wherein the application component comprises an application file.
 89. A communication system, comprising: a communication device, comprising: a controller unit; a digital signal processor coupled to the controller unit; a nonvolatile storage device coupled to the controller unit, comprising: a changeable area, wherein the changeable area further comprises a system area, said system area comprising an application component and a secure area coupled to the application component; and a server system capable of communicating through a secure medium with the application component.
 90. The communication system of claim 89, wherein the server system is capable of communicating through the secure medium with the secure area.
 91. The communication system of claim 90, wherein the system area is not modifiable by a user of the communication device.
 92. The communication system of claim 89, wherein the communication device is a personal digital assistant.
 93. The communication system of claim 89, wherein the nonvolatile storage device is a Flash memory.
 94. The communication system of claim 89, wherein the application component comprises an application file.
 95. A communication system, comprising: a communication device, comprising: a controller unit; a digital signal processor coupled to the controller unit; a nonvolatile storage device coupled to the controller unit, comprising: a changeable area, wherein the changeable area further comprises an application component and a communication protocol component coupled to the application component; and, one or more servers capable of communicating through a secure medium with the application component.
 96. The communication system of claim 95, wherein the communication protocol component is a smart messaging service component for mobile devices.
 97. The communication system of claim 96, further comprising: one or more smart messaging service servers capable of communicating through a communications medium with the smart messaging service component; and, wherein the one or more servers that communicate with the application component are web servers.
 98. The communication system of claim 97, wherein the communications medium is from the group consisting essentially of smart messaging service wireless link, Code Division Multiple Access, and Global Mobile System.
 99. The communication system of claim 96, wherein the communication device is from the group consisting essentially of Smart phone, smart messaging service capable device, and mobile phone device.
 100. The communication system of claim 95, wherein the nonvolatile storage device is a Flash memory.
 101. The communication system of claim 95, wherein the application component comprises an application file.
 102. A communication system, comprising: a communication device, comprising: a controller unit; a digital signal processor coupled to the controller unit; a nonvolatile storage device coupled to the controller unit, comprising: a changeable area, wherein the changeable area further comprises a system area in the nonvolatile storage device, said system area comprising an application component and a communication protocol component coupled to the application component; and, one or more servers capable of communicating through a secure medium with the application component.
 103. The communication system of claim 102, wherein the communication protocol component is a smart messaging service component for mobile devices.
 104. The communication system of claim 103, further comprising: one or more smart messaging service servers capable of communicating through a communications medium with the smart messaging service component; and, wherein the one or more servers that communicate with the application component are web servers.
 105. The communication system of claim 104, wherein the communications medium is from the group consisting essentially of smart messaging service wireless link, Code Division Multiple Access, and Global Mobile System.
 106. The communication system of claim 103, wherein the communication device is from the group consisting essentially of Smart phone, smart messaging service capable device, and mobile phone device.
 107. The communication system of claim 102, wherein the nonvolatile storage device is a Flash memory.
 108. The communication system of claim 102, wherein the application component comprises an application file.
 109. The communication system of claim 102, wherein the system area is not modifiable by a user of the communication device.
 110. An electronic device security and tracking system, comprising: one or more clients, wherein the clients are electronic devices; and, a server computer system connected to each of the clients, wherein the server computer system is capable of tracking and locating each of the clients.
 111. The electronic device security and tracking system of claim 110, wherein the one or more clients connect to the server computer system through a firewall.
 112. The electronic device security and tracking system of claim 110, wherein the server computer system comprises: one or more web servers coupled to each of the clients, wherein the web servers include a website for the electronic device security and tracking system; one or more file transfer protocol servers coupled to each of the web servers; and one or more database servers connected to each of the web servers.
 113. The electronic device security and tracking system of claim 112, wherein the one or more database servers connect to each of the web servers through a firewall.
 114. The electronic device security and tracking system of claim 112, wherein the web servers include a primary server coupled to a plurality of secondary servers.
 115. The electronic device security and tracking system of claim 114, wherein the client will access the website on the primary server and if unable will try to access the secondary servers to determine status of the primary server.
 116. A method for tracking, locating and disabling an electronic device, comprising: activating the electronic device; transferring control to a BIOS component after activation; transferring control to a non-viewable component from the BIOS component; verifying that an application component operated correctly during a previous device activation; and, continuing with activation of the electronic device if the application component operated correctly during the previous device activation.
 117. The method of claim 116, wherein activating the electronic device comprises activating a power on self test of the electronic device.
 118. The method of claim 117, wherein transferring control to a BIOS component comprises transferring control to a BIOS component during power on self test.
 119. The method of claim 118, further comprising: determining if the electronic device has been disabled; displaying system information and unlock key if the electronic device is disabled; prompting a user of the electronic device to enter activation password to re-enable electronic device if the electronic device is disabled; determining if a bootable operating system partition exists; rebooting the electronic device to restart power on self test; and, proceeding with booting the electronic device until it stops booting if no bootable operating system partition exists.
 120. The method of claim 119, further comprising: determining if a hidden partition exists if the electronic device is not disabled; transferring control to a non-viewable component if the hidden partition exists; and, creating a hidden partition if the hidden partition does not exist.
 121. The method of claim 120, further comprising rebuilding the hidden partition from a recovery media if the bootable operating system partition exists.
 122. The method of claim 120, wherein transferring control to a non-viewable component if the hidden partition exists, comprises: checking the communication area to determine if an application component operated correctly during last device boot; and, returning control to power on self test to proceed with booting the electronic device if the application component operated correctly during last device boot.
 123. The method of claim 122, wherein transferring control to a non-viewable component if the hidden partition exists, further comprises: prompting that the electronic device will be disabled within a number of device boots unless corrective action is taken if the application component did not operate correctly during last device boot; disabling the electronic device if the number of device boots has been reached; and, prompting for an activation password if the number of device boots has been reached.
 124. The method of claim 123, wherein transferring control to a non-viewable component if the hidden partition exists, further comprises restoring the application component from a backup fileset if the application component did not operate correctly during last device boot.
 125. The method of claim 123, wherein the number of device boots is five.
 126. The method of claim 125, wherein power on self test proceeds with booting the electronic device by transferring control to the application component, comprising: executing system processes and an application program contained in the application component; checking if the application component is operating correctly; and, communicating to the BIOS component if the application component is operating correctly.
 127. The method of claim 126, wherein power on self test proceeds with booting the electronic device by transferring control to the application component, further comprising: detecting an Internet connection on the electronic device; attempting to contact a primary server; and, sending an encrypted message to the primary server if successful in contacting the primary server.
 128. The method of claim 127, wherein power on self test proceeds with booting the electronic device by transferring control to the application component, further comprising: receiving a response from the primary server, wherein the response indicates status of whether or not the electronic device is reported stolen; waiting a random interval before sending another encrypted message to the primary server if the electronic device is not reported stolen; and, performing actions based on user selected service options if the electronic device is reported stolen.
 129. The method of claim 128, wherein the actions include disabling the electronic device or erasing hard disk drive.
 130. The method of claim 128, wherein power on self test proceeds with booting the electronic device by transferring control to the application component, further comprising: informing the communication area that the electronic device has been disabled if the user had selected the disable electronic device service; sending an encrypted message to the secondary server if not successful in contacting the primary server; warning the user that the primary server and secondary server can not be accessed if not successful in contacting the primary server or secondary server; and, disabling the electronic device after five device boots if an override code is not entered.
 131. The method of claim 130, wherein specialized hardware on the electronic device checks if the application component is operating correctly.
 132. The method of claim 130, wherein the message is encrypted by security hardware and includes the electronic device serial number or model number.
 133. The method of claim 130, wherein the encrypted message to the secondary server requests the status of the primary server.
 134. The method of claim 130, wherein warning the user that the primary server and secondary server cannot be accessed comprises requesting the user correct the problem within five device boots or enter an override code to continue operation of the device.
 135. The method of claim 134, wherein the override code is obtained from a website, call center or automated response system.
 136. The method of claim 117, wherein continuing with activation of the electronic device comprises returning control to power on self test to proceed with booting the electronic device if the application component operated correctly during a previous device boot.
 137. The method of claim 116, wherein verifying that the application component operated correctly comprises checking a communication area to determine if the application component operated correctly during a previous device boot.
 138. A machine-readable medium that provides instructions, which when executed by a machine, cause said machine to perform operations comprising: activating an electronic device; transferring control to a BIOS component after activation; transferring control to a non-viewable component from the BIOS component; verifying that an application component operated correctly during a previous device activation; and, continuing with activation of the electronic device if the application component operated correctly during the previous device activation.
 139. The machine-readable medium of claim 138, wherein activating the electronic device comprises activating a power on self test of the electronic device.
 140. The machine-readable medium of claim 139, wherein transferring control to a BIOS component comprises transferring control to a BIOS component during power on self test.
 141. The machine-readable medium of claim 140, further comprising: determining if the electronic device has been disabled; displaying system information and unlock key if the electronic device is disabled; prompting a user of the electronic device to enter activation password to re-enable electronic device if the electronic device is disabled; determining if a bootable operating system partition exists; rebooting the electronic device to restart power on self test; and, proceeding with booting the electronic device until it stops booting if no bootable operating system partition exists.
 142. The machine-readable medium of claim 141, further comprising: determining if a hidden partition exists if the electronic device is not disabled; transferring control to a non-viewable component if the hidden partition exists; and, creating a hidden partition if the hidden partition does not exist.
 143. The machine-readable medium of claim 142, further comprising rebuilding the hidden partition from a recovery media if the bootable operating system partition exists.
 144. The machine-readable medium of claim 142, wherein transferring control to a non-viewable component if the hidden partition exists, comprises: checking the communication area to determine if an application component operated correctly during last device boot; and, returning control to power on self test to proceed with booting the electronic device if the application component operated correctly during last device boot.
 145. The machine-readable medium of claim 144, wherein transferring control to a non-viewable component if the hidden partition exists, further comprises: prompting that the electronic device will be disabled within a number of device boots unless corrective action is taken if the application component did not operate correctly during last device boot; disabling the electronic device if the number of device boots has been reached; and, prompting for an activation password if the number of device boots has been reached.
 146. The machine-readable medium of claim 145, wherein transferring control to a non-viewable component if the hidden partition exists, further comprises restoring the application component from a backup fileset.
 147. The machine-readable medium of claim 145, wherein the number of device boots is five.
 148. The machine-readable medium of claim 147, wherein power on self test proceeds with booting the electronic device by transferring control to the application component, comprising: executing system processes and an application program contained in the application component; checking if the application component is operating correctly; and, communicating to the BIOS component if the application component is operating correctly.
 149. The machine-readable medium of claim 148, wherein power on self test proceeds with booting the electronic device by transferring control to the application component, further comprising: detecting an Internet connection on the electronic device; attempting to contact a primary server; and, sending an encrypted message to the primary server if successful in contacting the primary server.
 150. The machine-readable medium of claim 149, wherein power on self test proceeds with booting the electronic device by transferring control to the application component, further comprising: receiving a response from the primary server, wherein the response indicates status of whether or not the electronic device is reported stolen; waiting a random interval before sending another encrypted message to the primary server if the electronic device is not reported stolen; and, performing actions based on user selected service options if the electronic device is reported stolen.
 151. The machine-readable medium of claim 150, wherein the actions include disabling the electronic device or erasing hard disk drive.
 152. The machine-readable medium of claim 150, wherein power on self test proceeds with booting the electronic device by transferring control to the application component, further comprising: informing the communication area that the electronic device has been disabled if the user had selected the disable electronic device service; sending an encrypted message to the secondary server if not successful in contacting the primary server; warning the user that the primary server and secondary server can not be accessed if not successful in contacting the primary server or secondary server; and, disabling the electronic device after five device boots if an override code is not entered.
 153. The machine-readable medium of claim 152, wherein specialized hardware on the electronic device checks if the application component is operating correctly.
 154. The machine-readable medium of claim 152, wherein the message is encrypted by security hardware and includes the electronic device serial number or model number.
 155. The machine-readable medium of claim 152, wherein the encrypted message to the secondary server requests the status of the primary server.
 156. The machine-readable medium of claim 152, wherein warning the user that the primary server and secondary server cannot be accessed comprises requesting the user correct the problem within five device boots or enter an override code to continue operation of the device.
 157. The machine-readable medium of claim 156, wherein the override code is obtained from a website, call center or automated response system.
 158. The machine-readable medium of claim 139, wherein continuing with activation of the electronic device comprises returning control to power on self test to proceed with booting the electronic device if the application component operated correctly during a previous device boot.
 159. The machine-readable medium of claim 138, wherein verifying that the application component operated correctly comprises checking a communication area to determine if the application component operated correctly during a previous device boot.
 160. A method for tracking, locating, and disabling an electronic device including a BIOS component, comprising: determining if the electronic device has been disabled; displaying system information and unlock key if the electronic device is disabled; prompting a user of the electronic device to enter activation password to re-enable electronic device if the electronic device is disabled; determining if a bootable operating system partition exists; restarting the electronic device to allow the device to boot an operating system; and, proceeding with booting the electronic device until it stops booting if no bootable operating system partition exists.
 161. The method of claim 160, further comprising: determining if a hidden partition exists if the electronic device is not disabled; transferring control to a non-viewable component if the hidden partition exists; and, creating a hidden partition if the hidden partition does not exist.
 162. The method of claim 161, further comprising rebuilding the hidden partition from a recovery media if the bootable operating system partition exists.
 163. A machine-readable medium that provides instructions, which when executed by a machine, cause said machine to perform operations comprising: determining if an electronic device has been disabled; displaying system information and unlock key if the electronic device is disabled; prompting a user of the electronic device to enter activation password to re-enable electronic device if the electronic device is disabled; determining if a bootable operating system partition exists; restarting the electronic device to allow the device to boot an operating system; and, proceeding with booting the electronic device until it stops booting if no bootable operating system partition exists.
 164. The machine-readable medium of claim 163, further comprising: determining if a hidden partition exists if the electronic device is not disabled; transferring control to a non-viewable component if the hidden partition exists; and, creating a hidden partition if the hidden partition does not exist.
 165. The machine-readable medium of claim 164, further comprising rebuilding the hidden partition from a recovery media if the bootable operating system partition exists.
 166. A method for tracking, locating and disabling an electronic device including a nonviewable component, comprising: checking if an application component operated correctly during last power-up of the device; and, placing the device under control of power on self test to proceed with powering-up the device if the application component operated correctly during last device power-up.
 167. The method of claim 166, further comprising: prompting that the electronic device will be disabled within a number of device power-ups unless corrective action is taken if the application component did not operate correctly during last device power-up; disabling the electronic device if the number of device power-ups has been reached; and, prompting for an activation password if the number of device power-ups has been reached.
 168. The method of claim 167, further comprising restoring the application component from a backup fileset if the application component did not operate correctly during last device power-up.
 169. The method of claim 167, wherein the number of device power-ups is five.
 170. The method of claim 166, wherein powering-up the device includes allowing the device to boot an operating system.
 171. A machine-readable medium that provides instructions, which when executed by a machine, cause said machine to perform operations comprising: checking if an application component operated correctly during last power-up of an electronic device; and placing the device under control of power on self test to proceed with powering-up the device if the application component operated correctly during last device power-up.
 172. The machine-readable medium of claim 171, further comprising: prompting that the electronic device will be disabled within a number of device power-ups unless corrective action is taken if the application component did not operate correctly during last device power-up; disabling the electronic device if the number of device power-ups has been reached; and prompting for an activation password if the number of device power-ups has been reached.
 173. The machine-readable medium of claim 172, further comprising restoring the application component from a backup fileset if the application component did not operate correctly during last device power-up.
 174. The machine-readable medium of claim 172, wherein the number of device power-ups is five.
 175. The machine-readable medium of claim 171, wherein powering-up the device includes allowing the device to boot an operating system.
 176. A method for tracking, locating, and disabling an electronic device including an application component, comprising: executing system processes and an application program contained in an application component; checking if the application component is operating correctly; and communicating to a BIOS component if the application component is operating correctly.
 177. The method of claim 176, further comprising: detecting an Internet connection on the electronic device; attempting to contact a primary server; and sending an encrypted message to the primary server if successful in contacting the primary server.
 178. The method of claim 177, further comprising: receiving a response from the primary server, wherein the response indicates status of whether or not the electronic device is reported stolen; waiting a random interval before sending another encrypted message to the primary server if the electronic device is not reported stolen; and performing actions based on user selected service options if the electronic device is reported stolen.
 179. The method of claim 178, wherein the actions include disabling the electronic device or erasing hard disk drive.
 180. The method of claim 178, further comprising: informing a communication area that the electronic device has been disabled if the user had selected the disable electronic device service; sending an encrypted message to a secondary server if not successful in contacting the primary server; warning the user that the primary server and secondary server can not be accessed if not successful in contacting the primary server or secondary server; and disabling the electronic device after five attempts at contacting the primary server or secondary server.
 181. The method of claim 180, wherein specialized hardware on the electronic device checks if the application component is operating correctly.
 182. The method of claim 180, wherein the message is encrypted by security hardware and includes the electronic device serial number or model number.
 183. The method of claim 180, wherein the encrypted message to the secondary server requests the status of the primary server.
 184. The method of claim 180, wherein warning the user that the primary server and secondary server cannot be accessed comprises requesting the user correct the problem within five device boots or enter an override code to continue operation of the device.
 185. The method of claim 184, wherein the override code is obtained from a website, call center or automated response system.
 186. A machine-readable medium that provides instructions, which when executed by a machine, cause said machine to perform operations comprising: executing system processes and an application program contained in an application component; checking if the application component is operating correctly; and, communicating to a BIOS component if the application component is operating correctly.
 187. The machine-readable medium of claim 186, further comprising: detecting an Internet connection on the electronic device; attempting to contact a primary server; and, sending an encrypted message to the primary server if successful in contacting the primary server.
 188. The machine-readable medium of claim 187, further comprising: receiving a response from the primary server, wherein the response indicates status of whether or not the electronic device is reported stolen; waiting a random interval before sending another encrypted message to the primary server if the electronic device is not reported stolen; and, performing actions based on user selected service options if the electronic device is reported stolen.
 189. The machine-readable medium of claim 188, wherein the actions include disabling the electronic device or erasing hard disk drive.
 190. The machine-readable medium of claim 188, further comprising: informing a communication area that the electronic device has been disabled if the user had selected the disable electronic device service; sending an encrypted message to a secondary server if not successful in contacting the primary server; warning the user that the primary server and secondary server can not be accessed if not successful in contacting the primary server or secondary server; and, disabling the electronic device after five attempts at contacting the primary server or secondary server.
 191. The machine-readable medium of claim 190, wherein specialized hardware on the electronic device checks if the application component is operating correctly.
 192. The machine-readable medium of claim 190, wherein the message is encrypted by security hardware and includes the electronic device serial number or model number.
 193. The machine-readable medium of claim 190, wherein the encrypted message to the secondary server requests the status of the primary server.
 194. The machine-readable medium of claim 190, wherein warning the user that the primary server and secondary server cannot be accessed comprises requesting the user correct the problem within five device boots or enter an override code to continue operation of the device.
 195. The machine-readable medium of claim 194, wherein the override code is obtained from a website, call center or automated response system.
 196. An electronic device security and tracking system, comprising: a client device application including an encryption/decryption module, wherein the module directly transmits and receives data to and from the client device application; and, a server device application including an encryption/decryption module coupled to the client device application through a communication medium, wherein the module directly transmits and receives data to and from the server device application.
 197. The electronic device security and tracking system of claim 196, wherein the communication medium uses a hyper-text transfer protocol.
 198. The electronic device security and tracking system of claim 196, further comprising wherein the encryption/decryption module encrypts and encodes data for transmission and decrypts and decodes received data.
 199. The electronic device security and tracking system of claim 198, wherein the client device application sends query information to the server device application.
 200. The electronic device security and tracking system of claim 199, wherein the query information is sent at randomly selected times.
 201. The electronic device security and tracking system of claim 199, wherein the query information asks if the electronic device has been reported stolen.
 202. The electronic device security and tracking system of claim 201, wherein the query information is encrypted into a binary format.
 203. The electronic device security and tracking system of claim 202, wherein the binary encrypted query information is encoded into American Standard Code of Information Interchange text format.
 204. The electronic device security and tracking system of claim 203, wherein the binary encrypted query information is encoded by: selecting a subgroup of bits from one or more bytes of query information data; passing the subgroup of bits to an encoding function that performs binary mapping operations on the subgroup of bits to generate an encoded byte; and, encoding the next one or more bytes of data from the binary encrypted query information if the end of the binary encrypted query information has not been reached.
 205. The electronic device security and tracking system of claim 204, wherein the binary mapping operations further comprises mapping of the subgroup of bits to a character that may be printed and displayed.
 206. The electronic device security and tracking system of claim 205, wherein every three bytes of query information data is mapped to four bytes of encoded data.
 207. The electronic device security and tracking system of claim 204, wherein the subgroup of bits is six bits.
 208. The electronic device security and tracking system of claim 204, further comprising: storing the byte of data in a first variable, wherein the byte of data is made up of bits; storing the subgroup of bits from the byte of data in a second variable; and, storing the encoded byte into a data structure.
 209. The electronic device security and tracking system of claim 208, wherein the data structure is an array of bytes.
 210. The electronic device security and tracking system of claim 203, wherein the encoded American Standard Code of Information Interchange text format query information is received by the server device application.
 211. The electronic device security and tracking system of claim 210, wherein the American Standard Code of Information Interchange text format query information is decoded into the binary format query information.
 212. The electronic device security and tracking system of claim 211, wherein the binary format query information is decrypted into the query information.
 213. The electronic device security and tracking system of claim 211, wherein the American Standard Code of Information Interchange text format query information is decoded by: selecting a byte of data; passing the byte of data to a decoding function that returns a decoded byte; extracting the lower six bits of the decoded byte and discarding the upper two bits, wherein the lower six bits are appended to a stream of bits that form consecutive bytes; and, decoding the next bytes of data from the American Standard Code of Information Interchange text format query information if the end of the American Standard Code of Information Interchange text format query information has not been reached.
 214. The electronic device security and tracking system of claim 213, wherein the decoding function further comprises mapping the American Standard Code of Information Interchange byte of data to the binary format query information data byte.
 215. The electronic device security and tracking system of claim 213, further comprising storing the consecutive bytes into a data structure.
 216. The electronic device security and tracking system of claim 215, wherein the data structure is an array of bytes.
 217. The electronic device security and tracking system of claim 198, wherein the client device application send messages to the server device application.
 218. The electronic device security and tracking system of claim 217, wherein the server device application sends messages to the client device application.
 219. The electronic device security and tracking system of claim 218, wherein the messages are short messaging service messages.
 220. The electronic device security and tracking system of claim 219, wherein the message is encrypted into a binary format.
 221. The electronic device security and tracking system of claim 220, wherein the message is encrypted by: storing electronic device information into a first variable; jumbling the electronic device information; storing the jumbled device information into a second variable; passing the jumbled device information and a secret command to an encryption function that returns an encrypted array of bytes; and, encoding the encrypted array of bytes into American Standard Code of Information Interchange text format.
 222. The electronic device security and tracking system of claim 221, wherein jumbling further comprises shuffling the device information.
 223. The electronic device security and tracking system of claim 222, wherein the encryption function comprises performing symmetric encryption on the jumbled device information using a built-in key.
 224. The electronic device security and tracking system of claim 221, wherein encoding the encrypted array of bytes comprises: selecting a subgroup of bits from one or more bytes in the encrypted array of bytes; passing the subgroup of bits to an encoding function that performs binary mapping operations on the subgroup of bits to generate an encoded byte; and, encoding the next one or more bytes of data from the encrypted array of bytes if the end of the encrypted array of bytes has not been reached.
 225. The electronic device security and tracking system of claim 224, wherein the binary mapping operations further comprises mapping of the subgroup of bits to a character that may be printed and displayed.
 226. The electronic device security and tracking system of claim 225, wherein every three bytes of query information data is mapped to four bytes of encoded data.
 227. The electronic device security and tracking system of claim 224, wherein the subgroup of bits is six bits.
 228. The electronic device security and tracking system of claim 224, further comprising: storing the byte of data in a first variable, wherein the byte of data is made up of bits; storing the subgroup of bits from the byte of data in a second variable; and, storing the encoded byte into a data structure.
 229. The electronic device security and tracking system of claim 228, wherein the data structure is an array of bytes.
 230. The electronic device security and tracking system of claim 221, wherein the encoded array of bytes is received by the server device application.
 231. The electronic device security and tracking system of claim 230, wherein the encoded array of bytes is decoded into the binary format.
 232. The electronic device security and tracking system of claim 231, wherein decoding into the binary format comprises: selecting a byte of data; passing the byte of data to a decoding function that returns a decoded byte; extracting the lower six bits of the decoded byte and discarding the upper two bits, wherein the lower six bits are appended to a stream of bits that form consecutive bytes; and, decoding the next bytes of data from the encoded array of bytes if the end of the array of bytes has not been reached.
 233. The electronic device security and tracking system of claim 232, wherein the decoding function further comprises mapping the byte of data to the binary format.
 234. The electronic device security and tracking system of claim 232, further comprising storing the consecutive bytes into a data structure.
 235. The electronic device security and tracking system of claim 234, wherein the data structure is an array of bytes.
 236. The electronic device security and tracking system of claim 231, wherein the decoded array of bytes is decrypted into the short messaging service message.
 237. The electronic device security and tracking system of claim 236, wherein decrypting into the message comprises: passing a decoded byte into a decryption function that returns a decrypted byte; extracting the jumbled device information and the secret command from the decrypted byte; and, unjumbling the jumbled device information to determine the device information.
 238. The electronic device security and tracking system of claim 237, wherein unjumbling further comprises unshuffling the device information.
 239. The electronic device security and tracking system of claim 238, wherein the decryption function comprises performing symmetric decryption on the decoded byte using a built-in key.
 240. A method of encoding data, comprising: selecting a subgroup of bits from one or more bytes of binary encrypted information, wherein the binary encrypted information is for tracking, locating, and disabling an electronic device; passing the subgroup of bits to an encoding function that performs binary mapping operations on the subgroup of bits to generate an encoded byte; and, encoding the next one or more bytes of binary encrypted information if the end of the binary encrypted information has not been reached.
 241. The method of claim 240, wherein the binary encrypted query information is encoded into American Standard Code of Information Interchange text format.
 242. The method of claim 240, wherein the binary mapping operations further comprises mapping of the subgroup of bits to a character that may be printed and displayed.
 243. The method of claim 242, wherein every three bytes of binary encrypted information is mapped to four bytes of encoded data.
 244. The method of claim 240, wherein the subgroup of bits is six bits.
 245. The method of claim 240, further comprising: storing the one or more bytes of binary encrypted information in a first variable, wherein each byte of data is made up of bits; storing the subgroup of bits from the one or more bytes of data in a second variable; and, storing the encoded byte into a data structure.
 246. The method of claim 245, wherein the data structure is an array of bytes.
 247. A method of decoding data, comprising: selecting a byte of American Standard Code of Information Interchange text format information, wherein the American Standard Code of Information Interchange text format information byte is for tracking, locating, and disabling an electronic device; passing the byte to a decoding function that returns a decoded byte; and, extracting the lower six bits of the decoded byte and discarding the upper two bits, wherein the lower six bits are appended to a stream of bits that form consecutive bytes; decoding the next bytes of data from the American Standard Code of Information Interchange text format information if the end of the American Standard Code of Information Interchange text format information has not been reached.
 248. The method of claim 247, wherein the decoding function further comprises mapping the byte of American Standard Code of Information Interchange text format information to the binary format query information data byte.
 249. The method of claim 247, further comprising storing the consecutive bytes into a data structure.
 250. The method of claim 249, wherein the data structure is an array of bytes.
 251. A machine-readable medium that provides instructions, which when executed by a machine, cause said machine to perform operations comprising: selecting a subgroup of bits from one or more bytes of binary encrypted information, wherein the binary encrypted information is for tracking, locating, and disabling an electronic device; passing the subgroup of bits to an encoding function that performs binary mapping operations on the subgroup of bits to generate an encoded byte; and, encoding the next one or more bytes of binary encrypted information if the end of the binary encrypted information has not been reached.
 252. The machine-readable medium of claim 251, wherein the binary encrypted query information is encoded into American Standard Code of Information Interchange text format.
 253. The machine-readable medium of claim 251, wherein the binary mapping operations further comprises mapping of the subgroup of bits to a character that may be printed and displayed.
 254. The machine-readable medium of claim 253, wherein every three bytes of binary encrypted information is mapped to four bytes of encoded data.
 255. The machine-readable medium of claim 251, wherein the subgroup of bits is six bits.
 256. The machine-readable medium of claim 251, further comprising: storing the one or more bytes of binary encrypted information in a first variable, wherein each byte of data is made up of bits; storing the subgroup of bits from the one or more bytes of data in a second variable; and, storing the encoded byte into a data structure.
 257. The machine-readable medium of claim 256, wherein the data structure is an array of bytes.
 258. A machine-readable medium that provides instructions, which when executed by a machine, cause said machine to perform operations comprising: selecting a byte of American Standard Code of Information Interchange text format information, wherein the American Standard Code of Information Interchange text format information byte is for tracking, locating, and disabling an electronic device; passing the byte to a decoding function that returns a decoded Byte; extracting the lower six bits of the decoded byte and discarding the upper two bits, wherein the lower six bits are appended to a stream of bits that form consecutive bytes; and, decoding the next bytes of data from the American Standard Code of Information Interchange text format information if the end of the American Standard Code of Information Interchange text format information has not been reached.
 259. The machine-readable medium of claim 258, wherein the decoding function further comprises mapping the byte of American Standard Code of Information Interchange text format information to the binary format query information data byte.
 260. The machine-readable medium of claim 258, further comprising storing the consecutive bytes into a data structure.
 261. The machine-readable medium of claim 260, wherein the data structure is an array of bytes.
 262. A method for including an electronic device security and tracking system BIOS component into a system BIOS read-only-memory, comprising: creating a data structure; placing an address of the data structure into the system build file; placing BIOS component into a system build file, wherein the BIOS component accesses the data structure using the address; and, placing into the system build file a call to the BIOS component just before a call to the system BIOS.
 263. The method of claim 262, wherein the data structure includes electronic device system information, software for saving and restoring critical information in a secure non-volatile area, and a recovery media read function pointer. 